linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Mel Gorman <mel@csn.ul.ie>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"minchan.kim@gmail.com" <minchan.kim@gmail.com>,
	Christoph Lameter <cl@linux.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUGFIX][mm][PATCH] fix migration race in rmap_walk
Date: Mon, 26 Apr 2010 18:28:38 +0900	[thread overview]
Message-ID: <20100426182838.2cab9844.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20100426084901.15c09a29.kamezawa.hiroyu@jp.fujitsu.com>

On Mon, 26 Apr 2010 08:49:01 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:

> On Sat, 24 Apr 2010 11:43:24 +0100
> Mel Gorman <mel@csn.ul.ie> wrote:

> > It looks nice but it still broke after 28 hours of running. The
> > seq-counter is still insufficient to catch all changes that are made to
> > the list. I'm beginning to wonder if a) this really can be fully safely
> > locked with the anon_vma changes and b) if it has to be a spinlock to
> > catch the majority of cases but still a lazy cleanup if there happens to
> > be a race. It's unsatisfactory and I'm expecting I'll either have some
> > insight to the new anon_vma changes that allow it to be locked or Rik
> > knows how to restore the original behaviour which as Andrea pointed out
> > was safe.
> > 
> Ouch. 

Ok, reproduced. Here is status in my test + printk().

 * A race doesn't seem to happen if swap=off. 
    I need to swapon to cause the bug.
 * Before unmap, mapcount=1, SwapCache for anonymous memory.
   old page's flag was SWAPCACHE, Active, Uptodate, Referenced, Locked.
 * After remap, mapcount=0, return code=0.
   new page's flag after remap was SwapCache, Active, Dirty, Uptodate, Referenced.

(Hmm, dirty bit can be added by try_to_unamp().)

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

  parent reply	other threads:[~2010-04-26  9:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23  3:01 KAMEZAWA Hiroyuki
2010-04-23  5:11 ` Minchan Kim
2010-04-23  5:27   ` KAMEZAWA Hiroyuki
2010-04-23  7:00     ` Minchan Kim
2010-04-23  7:17       ` KAMEZAWA Hiroyuki
2010-04-23  7:53         ` Minchan Kim
2010-04-23  7:55           ` KAMEZAWA Hiroyuki
2010-04-23  9:59 ` Mel Gorman
2010-04-23 15:58   ` Mel Gorman
2010-04-24  2:02     ` KAMEZAWA Hiroyuki
2010-04-24 10:43       ` Mel Gorman
2010-04-25 23:49         ` KAMEZAWA Hiroyuki
2010-04-26  2:53           ` KAMEZAWA Hiroyuki
2010-04-26  4:31             ` Minchan Kim
2010-04-26  4:06           ` Minchan Kim
2010-04-26  9:28           ` KAMEZAWA Hiroyuki [this message]
2010-04-26  9:48             ` Minchan Kim
2010-04-26  9:49               ` KAMEZAWA Hiroyuki
2010-04-26 10:07                 ` Minchan Kim
2010-04-26 11:36               ` Mel Gorman
2010-04-26  4:00     ` Minchan Kim

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=20100426182838.2cab9844.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=minchan.kim@gmail.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