From: Andrew Morton <akpm@osdl.org>
To: Hans Reiser <reiser@namesys.com>
Cc: hugh@veritas.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, lee.schermerhorn@hp.com,
Reiserfs-Dev@namesys.com
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 [thread overview]
Message-ID: <20060205011152.7f9b7aa9.akpm@osdl.org> (raw)
In-Reply-To: <43E5BB2E.5000203@namesys.com>
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.
next prev parent reply other threads:[~2006-02-05 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060205003039.3067e43c.akpm@osdl.org>
2006-02-05 8:45 ` Fw: Re: [PATCH] 2.6.16-rc-mm4 reiser4 calls try_to_unmap() with 1 arg -- now takes 2 Hans Reiser
2006-02-05 9:11 ` Andrew Morton [this message]
2006-02-05 18:42 ` Hans Reiser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060205011152.7f9b7aa9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Reiserfs-Dev@namesys.com \
--cc=hugh@veritas.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).