* dup_mmap() questions
@ 2005-02-16 23:15 Menyhart, Zoltan
0 siblings, 0 replies; only message in thread
From: Menyhart, Zoltan @ 2005-02-16 23:15 UTC (permalink / raw)
To: linux-kernel
We lock the semaphore of the old "mm" for write.
Usually we do this when the corresponding VMA list is being modified.
Does "dup_mmap()" modify the old VMA list ?
Or would a "down_read(&oldmm->mmap_sem)" be enough ?
Should not we lock for write the semaphore of the new "mm" ?
It is on the "mmlist", it can be seen.
The new "vma" is on the "anon" list and on the "vma_prio_tree",
can it be done without holding for write the semaphore of the new "mm" ?
Should not we hold for write the semaphore of the new "mm"
when the new "vma" is actually added ?
Is the "page_table_lock" enough ?
Apparently, the argument "oldmm" is equal to "current->mm".
Why do we pass it as an argument ?
Thanks.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-02-16 23:15 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-02-16 23:15 dup_mmap() questions Menyhart, Zoltan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).