From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751140Ab0DZEcB (ORCPT ); Mon, 26 Apr 2010 00:32:01 -0400 Received: from mail-iw0-f178.google.com ([209.85.223.178]:60538 "EHLO mail-iw0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750787Ab0DZEb7 (ORCPT ); Mon, 26 Apr 2010 00:31:59 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=trHk4GFspui6JWk2V8kaaYiKCUOFhXOGecBAhgM2zRupkOE665Uob5rQh/MbEBFPOD ilKvLi6Jev4S6mk/oDk87QlpYvgARkW2Sh2kC8/Ahm7dM328lHxoV9iWIuEE8ellBSnT X2hJJtILnOMy2BOhSENj1HCyAczpFlwaN3VMM= MIME-Version: 1.0 In-Reply-To: <20100426115347.2ee2a917.kamezawa.hiroyu@jp.fujitsu.com> References: <20100423120148.9ffa5881.kamezawa.hiroyu@jp.fujitsu.com> <20100423095922.GJ30306@csn.ul.ie> <20100423155801.GA14351@csn.ul.ie> <20100424110200.b491ec5f.kamezawa.hiroyu@jp.fujitsu.com> <20100424104324.GD14351@csn.ul.ie> <20100426084901.15c09a29.kamezawa.hiroyu@jp.fujitsu.com> <20100426115347.2ee2a917.kamezawa.hiroyu@jp.fujitsu.com> Date: Mon, 26 Apr 2010 13:31:59 +0900 Message-ID: Subject: Re: [BUGFIX][mm][PATCH] fix migration race in rmap_walk From: Minchan Kim To: KAMEZAWA Hiroyuki Cc: Mel Gorman , "linux-mm@kvack.org" , Christoph Lameter , "akpm@linux-foundation.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 26, 2010 at 11:53 AM, KAMEZAWA Hiroyuki wrote: > On Mon, 26 Apr 2010 08:49:01 +0900 > KAMEZAWA Hiroyuki wrote: > >> On Sat, 24 Apr 2010 11:43:24 +0100 >> Mel Gorman 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. Hmm, how about the race in fork() I pointed out ? >> > Forget this. Sorry for noise. Yes. It was due to my wrong explanation. Sorry for that, Kame. -- Kind regards, Minchan Kim