[PATCH 0/5] always lock the root anon_vma
in [Kernel]
|
Prev: [PATCH 1/5] rename anon_vma_lock to vma_lock_anon_vma
Next: [PATCH 3/5] track the root (oldest) anon_vma
From: Rik van Riel on 12 May 2010 13:50 This patch series implements Linus's suggestion of always locking the root anon_vma. Because the lock in other anon_vmas no longer protects anything at all, we cannot do the "lock dance" that Mel's earlier patches implements and instead need a root pointer in the anon_vma. The only subtlety these patches rely on is that the same_vma list is ordered from new to old, with the root anon_vma at the very end. This, together with the forward list walking in unlink_anon_vmas, ensures that the root anon_vma is the last one freed. The KSM refcount adds some additional complexity, because an anon_vma can stick around after the processes it was attached to have already exited. Patch 5/5 deals with that issue. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |