linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, mel@csn.ul.ie, y-goto@jp.fujitsu.com,
	hugh@veritas.com
Subject: Re: [RFC] memory unplug v5 [1/6] migration by kernel
Date: Thu, 14 Jun 2007 17:29:36 +0900	[thread overview]
Message-ID: <20070614172936.12b94ad7.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706140044400.22032@schroedinger.engr.sgi.com>

On Thu, 14 Jun 2007 00:47:46 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:

> On Thu, 14 Jun 2007, KAMEZAWA Hiroyuki wrote:
> 
> > In my understanding:
> > 
> > PageAnon(page) checks (page->mapping & 0x1). And, as you know, page->mapping
> > is not cleared even if the page is removed from rmap.
> 
> But in that case the refcount is zero. We will not migrate the page.
> 
yes. why we add dummy_vma to page here is 
==
0. page_count(page) check.
1. does try_to_unmap() and page->mapcount goes down to 0. page->count goes down to 1.
2. page->mapping is copied to newpage.
3. remove_migration_ptes is called against newpage->mapping.
==

If page is zapped while 0->1, newpage->mapping can be untrustable value.
My point is that if page->mapcount goes down to 0, we should be careful to
access page->mapping value.

But...during discussion with you, I found anon_vma is now freed by RCU...

Ugh, then, what I have to do is  rcu_read_lock() -> rcu_read_unlock() while
migrating anon ptes. If we can rcu read lock here, we don't need dummy_vma.
How about this ?

-Kame
p.s page_lock_anon_vma() locks anon_vma, not page.

==
page migratio by kernel v5.

Changelog V5->V6
 - removed dummy_vma and uses rcu_read_lock().

In usual, migrate_pages(page,,) is called with holoding mm->sem by systemcall.
(mm here is a mm_struct which maps the migration target page.)
This semaphore helps avoiding some race conditions.

But, if we want to migrate a page by some kernel codes, we have to avoid
some races. This patch adds check code for following race condition.

1. A page which is not mapped can be target of migration. Then, we have
   to check page_mapped() before calling try_to_unmap().

2. anon_vma can be freed while page is unmapped, but page->mapping remains as
   it was. We drop page->mapcount to be 0. Then we cannot trust page->mapping.
   So, use rcu_read_lock() to prevent anon_vma pointed by page->mapping will
   not be freed during migration.

Signed-Off-By: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>


---
 mm/migrate.c |   13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

Index: devel-2.6.22-rc4-mm2/mm/migrate.c
===================================================================
--- devel-2.6.22-rc4-mm2.orig/mm/migrate.c
+++ devel-2.6.22-rc4-mm2/mm/migrate.c
@@ -612,6 +612,7 @@ static int unmap_and_move(new_page_t get
 	int rc = 0;
 	int *result = NULL;
 	struct page *newpage = get_new_page(page, private, &result);
+	int rcu_locked = 0;
 
 	if (!newpage)
 		return -ENOMEM;
@@ -632,16 +633,24 @@ static int unmap_and_move(new_page_t get
 			goto unlock;
 		wait_on_page_writeback(page);
 	}
-
+	/* anon_vma should not be freed while migration. */
+	if (PageAnon(page)) {
+		rcu_read_lock();
+		rcu_locked = 1;
+	}
 	/*
 	 * Establish migration ptes or remove ptes
 	 */
-	try_to_unmap(page, 1);
+	if (page_mapped(page))
+		try_to_unmap(page, 1);
+
 	if (!page_mapped(page))
 		rc = move_to_new_page(newpage, page);
 
 	if (rc)
 		remove_migration_ptes(page, page);
+	if (rcu_locked)
+		rcu_read_unlock();
 
 unlock:
 	unlock_page(page);


--
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>

  reply	other threads:[~2007-06-14  8:29 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 [this message]
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
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=20070614172936.12b94ad7.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