Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754525Ab0KUPj7 (ORCPT ); Sun, 21 Nov 2010 10:39:59 -0500 Received: from mail-pz0-f46.google.com ([209.85.210.46]:48106 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754031Ab0KUPj5 (ORCPT ); Sun, 21 Nov 2010 10:39:57 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=DtrwleCyCTNhp4gH/5sHoM7fedHl0s5wRZaLOucUizglDguveRDoBtbwo2egAUcsCE jl89u00LL7UV+ZDwMnkyW6U7yFoMZ9hDvRDN4I0aa5YS3Rp89Tq6Fc3To1gowcnfF2kL n1eRMdPzpGVNbGF6NjAP27375f8IkC8z5cVh0= Date: Mon, 22 Nov 2010 00:39:49 +0900 From: Minchan Kim To: "Ted Ts'o" , linux-ext4@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andreas Dilger , Paul McKenney , Eric Sandeen Subject: Re: [BUG?] [Ext4] INFO: suspicious rcu_dereference_check() usage Message-ID: <20101121153949.GD20947@barrios-desktop> References: <20101121112611.GB4267@deepthought.bhanu.net> <20101121133024.GF23423@thunk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101121133024.GF23423@thunk.org> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1117 Lines: 30 On Sun, Nov 21, 2010 at 08:30:24AM -0500, Ted Ts'o wrote: > On Sun, Nov 21, 2010 at 07:26:11PM +0800, Arun Bhanu wrote: > > I saw this in kernel log messages while testing 2.6.37-rc2. I think it > > appeared while mounting an external hard-disk. I can't seem to > > reproduce it. > > I could be wrong but this looks like it's a bug in mm/migrate.c in > migrate_page_move_mapping(): it is calling radix_tree_lookup_slot() > without first taking an rcu_read_lock(). > > It was triggered by a memory allocation out of ext4_fill_super(), > which then triggered a memory compaction/migration, but I don't > believe it's otherwise related to the ext4 code. > > Over to the linux-mm folks for confirmation... I think it's no problem. That's because migration always holds lock_page on the file page. So the page couldn't remove from radix. -- Kind regards, Minchan Kim -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/