From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: mel@csn.ul.ie, linux-mm@kvack.org, y-goto@jp.fujitsu.com,
hugh@veritas.com
Subject: Re: [RFC] memory unplug v5 [1/6] migration by kernel
Date: Sat, 16 Jun 2007 00:36:10 +0900 [thread overview]
Message-ID: <20070616003610.2acbcbc8.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706150740510.7471@schroedinger.engr.sgi.com>
On Fri, 15 Jun 2007 07:41:42 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:
> On Fri, 15 Jun 2007, KAMEZAWA Hiroyuki wrote:
>
> > /*
> > - * Establish migration ptes or remove ptes
> > + * This is a corner case handling.
> > + * When a new swap-ache is read into, it is linked to LRU
> > + * and treated as swapcache but has no rmap yet.
> > + * Calling try_to_unmap() against a page->mapping==NULL page is
> > + * BUG. So handle it here.
> > + */
> > + if (!page->mapping)
> > + goto unlock;
> > + /*
> > + * By try_to_unmap(), page->mapcount goes down to 0 here. In this case,
> > + * we cannot notice that anon_vma is freed while we migrates a pages
> > + * This rcu_read_lock() delays freeing anon_vma pointer until the end
> > + * of migration. File cache pages are no problem because of page_lock()
> > */
> > + rcu_read_lock();
> > try_to_unmap(page, 1);
>
> page->mapping needs to be checked after rcu_read_lock. The mapping may be
> removed and the anon_vma dropped after you checked page->mapping.
>
page->mapping is not clearred when the kernel removing rmap (it will not be
cleared even if it is freed in my understanding)
...but your point seems reasonable. I'll fix it.
BTW, I'll not able to touch my box until next Friday.
Regards,
-Kame
--
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:[~2007-06-15 15:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 6:56 [RFC] memory unplug v5 [0/6] intro KAMEZAWA Hiroyuki
2007-06-14 6:59 ` [RFC] memory unplug v5 [1/6] migration by kernel KAMEZAWA Hiroyuki
2007-06-14 7:01 ` Christoph Lameter
2007-06-14 7:11 ` KAMEZAWA Hiroyuki
2007-06-14 7:22 ` Christoph Lameter
2007-06-14 7:41 ` KAMEZAWA Hiroyuki
2007-06-14 7:47 ` Christoph Lameter
2007-06-14 8:29 ` KAMEZAWA Hiroyuki
2007-06-14 14:19 ` Christoph Lameter
2007-06-14 16:02 ` KAMEZAWA Hiroyuki
2007-06-14 16:12 ` Christoph Lameter
2007-06-14 16:15 ` KAMEZAWA Hiroyuki
2007-06-14 18:04 ` Mel Gorman
2007-06-14 22:31 ` KAMEZAWA Hiroyuki
2007-06-15 9:43 ` KAMEZAWA Hiroyuki
2007-06-15 9:53 ` KAMEZAWA Hiroyuki
2007-06-15 14:41 ` Christoph Lameter
2007-06-15 15:36 ` KAMEZAWA Hiroyuki [this message]
2007-06-14 7:00 ` [RFC] memory unplug v5 [2/6] isolate lru page race fix KAMEZAWA Hiroyuki
2007-06-14 7:01 ` [RFC] memory unplug v5 [3/6] walk memory resources assist function KAMEZAWA Hiroyuki
2007-06-15 6:05 ` David Rientjes
2007-06-15 6:11 ` KAMEZAWA Hiroyuki
2007-06-14 7:03 ` [RFC] memory unplug v5 [4/6] page isolation KAMEZAWA Hiroyuki
2007-06-15 15:46 ` Dave Hansen
2007-06-15 16:59 ` KAMEZAWA Hiroyuki
2007-06-14 7:04 ` [RFC] memory unplug v5 [5/6] page unplug KAMEZAWA Hiroyuki
2007-06-15 6:04 ` David Rientjes
2007-06-15 6:12 ` KAMEZAWA Hiroyuki
2007-06-15 14:35 ` Christoph Lameter
2007-06-15 14:40 ` Andy Whitcroft
2007-06-15 15:52 ` Dave Hansen
2007-06-15 17:03 ` KAMEZAWA Hiroyuki
2007-06-15 21:09 ` Dave Hansen
2007-06-14 7:06 ` [RFC] memory unplug v5 [6/6] ia64 interface KAMEZAWA Hiroyuki
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=20070616003610.2acbcbc8.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=y-goto@jp.fujitsu.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