diff options
| author | Hugh Dickins <hugh@veritas.com> | 2004-04-17 03:50:14 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2004-04-17 03:50:14 -0700 |
| commit | e4cf8264fa0bbc0b113442df03ceb9606d2ec428 (patch) | |
| tree | db03c1a1a4b9160004bc9db3838ef063a763c70d /include/linux/node.h | |
| parent | 3ba9ac07443fbcf68424a12daeadae36d2bc8b23 (diff) | |
[PATCH] Fix vma corruption
It occurred to me that if vma and new_vma are one and the same, then
vma_relink_file will not do a good job of linking it after itself - in
that pretty unlikely case when move_page_tables fails.
And more generally, whenever copy_vma's vma_merge succeeds, we have no
guarantee that old vma comes before new_vma in the i_mmap lists, as we
need to satisfy Rajesh's point: that ordering is only guaranteed in the
newly allocated case.
We have to abandon the ordering method when/if we move from lists to
prio_trees, so this patch switches to the less glamorous use of
i_shared_sem exclusion, as in my prio_tree mremap.
Diffstat (limited to 'include/linux/node.h')
0 files changed, 0 insertions, 0 deletions
