From: Nick Piggin <npiggin@suse.de>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Christoph Lameter <clameter@engr.sgi.com>,
Jens Axboe <axboe@suse.de>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch] rfc: fix splice mapping race?
Date: Sun, 18 Jun 2006 12:11:43 +0200 [thread overview]
Message-ID: <20060618101143.GE14452@wotan.suse.de> (raw)
In-Reply-To: <1150624965.28517.55.camel@lappy>
On Sun, Jun 18, 2006 at 12:02:45PM +0200, Peter Zijlstra wrote:
> > In page migration, detect the missing mapping early and bail out if
> > that is the case: the page is not going to get un-truncated, so
> > retrying is just a waste of time.
> >
> > Signed-off-by: Nick Piggin <npiggin@suse.de>
>
> Looks sane, except the change in migrate (comment there). I like the
> remove_mapping() pre-conditions.
Thanks.
> > --- linux-2.6.orig/mm/migrate.c
> > +++ linux-2.6/mm/migrate.c
> > @@ -136,9 +136,13 @@ static int swap_page(struct page *page)
> > {
> > struct address_space *mapping = page_mapping(page);
> >
> > - if (page_mapped(page) && mapping)
> > + if (!mapping)
> > + return -EINVAL; /* page truncated. signal permanent failure */
>
> Here, I think you need to unlock the page too.
Bah, yes thanks... I'll post an updated patch after others have
had time to comment.
Nick
--
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-06-18 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 9:41 Nick Piggin
2006-06-18 10:02 ` Peter Zijlstra
2006-06-18 10:11 ` Nick Piggin [this message]
2006-06-19 7:29 ` Jens Axboe
2006-06-19 15:35 ` Christoph Lameter
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=20060618101143.GE14452@wotan.suse.de \
--to=npiggin@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=clameter@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox