From: Andrea Arcangeli <andrea@suse.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@osdl.org>, Hugh Dickins <hugh@veritas.com>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [patch][rfc] possible lock_page fix for Andrea's nopage vs invalidate race?
Date: Tue, 1 Aug 2006 16:27:49 +0200 [thread overview]
Message-ID: <20060801142749.GC6455@opteron.random> (raw)
In-Reply-To: <44CF3CB7.7030009@yahoo.com.au>
On Tue, Aug 01, 2006 at 09:36:23PM +1000, Nick Piggin wrote:
> Hi,
>
> Just like to get some thoughts on another possible approach to this
> problem, and whether my changelog and implementation actually capture
> the problem. This fix is actually something Andrea had proposed, so
> credit really goes to him.
The credit for this third possible fix goes to you for sorting out all
the details ;). This is perhaps the cleanest fix even if more
intrusive.
> I suppose we should think about fixing it some day?
I was thinking about this every few days too, but I already submitted
two fixes and I got somewhat contradictory reviews of them, so I
wasn't sure what to do given that for mainline it's mostly a DoS
because the VM lacks the proper bugchecks in the objrmap layer to
autodetect the leak (the bugchecks I'm talking about only exists only
in the sles9 VM, Hugh removed them while merging objrmap into
mainline, and the fact they existed in sles9 is why we noticed and
tracked down this leak). We already fixed the bug in sles9 a while ago
with my second fix, but I obviously agree we have to fix it in
mainline as well some day too, infact I wouldn't mind to add the
bugchecks too to be sure something like this doesn't go unnoticed
again (especially now that in sles10 we're in VM sync with mainline).
I really appreciate this third way being implemented. It looks quite
nice. Great work.
--
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>
next prev parent reply other threads:[~2006-08-01 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 11:36 Nick Piggin
2006-08-01 14:27 ` Andrea Arcangeli [this message]
2006-08-02 0:19 ` Nick Piggin
2006-08-03 16:04 ` Hugh Dickins
2006-08-05 3:52 ` Nick Piggin
2006-08-07 14:18 ` Nick Piggin
2006-08-07 14:58 ` Nick Piggin
2006-08-07 15:25 ` Hugh Dickins
2006-08-08 1:17 ` Nick Piggin
2006-08-07 17:05 ` Hugh Dickins
2006-08-08 1:14 ` Nick Piggin
2006-08-08 18:19 ` Hugh Dickins
2006-08-03 16:34 ` David Howells
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=20060801142749.GC6455@opteron.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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