Re: Fw: Re: [PATCH] 2.6.16-rc-mm4 reiser4 calls try_to_unmap() with 1 arg -- now takes 2

[Hans Reiser <reiser@namesys.com>]

Andrew Morton wrote:

>Hans Reiser <reiser@namesys.com> wrote:
>  
>
>>Umm, no, copy on capture needs to get enabled again as soon as we get
>> past issues outsiders care about, and start dealing again with improving
>> the code in the ways we think matter.  There are real problems that are
>> addressed by copy on capture.  That it has not been worked on since
>> 2.6.5 just sadly indicates how successful folks have been in distracting
>> us for so long.
>>    
>>
>
>Dinking with rmap internals from within a filesystem is a real problem. 
>Whatever needs to be done there should be done within core MM if it's done
>anywhere so it actually gets maintained by the people who are likely to
>break it.
>
>Something like
>http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc4/2.6.13-rc4-mm1/broken-out/add-page-becoming-writable-notification.patch
>might be what you're after.
>
>
>
>  
>
I don't actually care (at least I desire that I not have to care ;-) )
about the implementation of copy-on-capture so long as it works.  I am
sure vs will be happy to do it within core mm when we get to where he
can pay attention to it again.