From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: Fw: Re: [PATCH] 2.6.16-rc-mm4 reiser4 calls try_to_unmap() with 1 arg -- now takes 2 Date: Sun, 5 Feb 2006 01:11:52 -0800 Message-ID: <20060205011152.7f9b7aa9.akpm@osdl.org> References: <20060205003039.3067e43c.akpm@osdl.org> <43E5BB2E.5000203@namesys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: hugh@veritas.com, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, lee.schermerhorn@hp.com, Reiserfs-Dev@namesys.com Return-path: Received: from smtp.osdl.org ([65.172.181.4]:15232 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1751674AbWBEJMV (ORCPT ); Sun, 5 Feb 2006 04:12:21 -0500 To: Hans Reiser In-Reply-To: <43E5BB2E.5000203@namesys.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hans Reiser 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.