Re: mmu_notifier: close hole in fork

2008-01-31 Thread Christoph Lameter
On Fri, 1 Feb 2008, Andrea Arcangeli wrote: > Good catch! This was missing also in my #v5 (KVM doesn't need that > because the only possible cows on sptes can be generated by ksm, but > it would have been a problem for GRU). The more I think about it, the How do you think the GRU should know when

Re: mmu_notifier: close hole in fork

2008-01-31 Thread Andrea Arcangeli
On Thu, Jan 31, 2008 at 02:01:43PM -0800, Christoph Lameter wrote: > Talking to Robin and Jack we found taht we still have a hole during fork. > Fork may set a pte writeprotect. At that point the remote pte are > not marked readonly(!). Remote writes may occur to pages that are marked > readonly

mmu_notifier: close hole in fork

2008-01-31 Thread Christoph Lameter
Talking to Robin and Jack we found taht we still have a hole during fork. Fork may set a pte writeprotect. At that point the remote pte are not marked readonly(!). Remote writes may occur to pages that are marked readonly locally without this patch. mmu_notifier: Provide invalidate_range on for