From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Blaisorblade <blaisorblade@yahoo.it>,
linux-mm@kvack.org, Jeff Dike <jdike@addtoit.com>
Subject: Re: remap_file_pages support - lost messages?
Date: Wed, 11 Apr 2007 17:26:56 +1000 [thread overview]
Message-ID: <461C8DC0.1060509@yahoo.com.au> (raw)
In-Reply-To: <1176237622.18017.0.camel@lappy>
Peter Zijlstra wrote:
> On Mon, 2007-04-09 at 10:43 -0700, Andrew Morton wrote:
>
>>On Mon, 9 Apr 2007 16:12:57 +0200 Blaisorblade <blaisorblade@yahoo.it> wrote:
>>
>>
>>>Andrew, last week I sent to you the patchset for remap_file_pages protection
>>>support, against 2.6.21-rc5-mm3. I got no response at all on that, even if I
>>>thought it would be merged in -mm. What happened? Should I resend it?
>>
>>I saw them, and hung onto them for a week in the hope that someone would
>>get in and review them, but nobody did.
>>
>>So I suppose you should resend, please. Try cc'ing lkml as well - there
>>seems to be plenty of surplus labour over there ;)
>
>
> I intended to go over it in detail, I just haven't found the time
> yet :-(
Ditto. The fault handler / sigsegv code still seems a little bit unfortunate
(if it can't be improved then maybe it can at least be ifdef'ed), however I
hadn't seen the patchset since it had been using some weird pte encoding
conventions. Now that it is using a more formal encoding and its own not
present bit, that part of it looks much cleaner.
--
SUSE Labs, Novell Inc.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-04-11 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 14:12 remap_file_pages support - lost messages? Blaisorblade
2007-04-09 17:43 ` Andrew Morton
2007-04-10 20:40 ` Peter Zijlstra
2007-04-11 7:26 ` Nick Piggin [this message]
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=461C8DC0.1060509@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-mm@kvack.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.