From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by kanga.kvack.org (Postfix) with ESMTP id CB2906B0031 for ; Thu, 13 Feb 2014 20:22:09 -0500 (EST) Received: by mail-ee0-f54.google.com with SMTP id e53so5370351eek.27 for ; Thu, 13 Feb 2014 17:22:09 -0800 (PST) Received: from trent.utfs.org (trent.utfs.org. [2a03:3680:0:3::67]) by mx.google.com with ESMTP id f45si7482919eep.194.2014.02.13.17.22.07 for ; Thu, 13 Feb 2014 17:22:08 -0800 (PST) Date: Thu, 13 Feb 2014 17:22:06 -0800 (PST) From: Christian Kujau Subject: Re: 3.14.0-rc2: WARNING: at mm/slub.c:1007 In-Reply-To: <20140214011453.GP13997@dastard> Message-ID: References: <20140213222602.GK13997@dastard> <20140214011453.GP13997@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: Dave Chinner Cc: LKML , xfs@oss.sgi.com, linux-mm@kvack.org On Fri, 14 Feb 2014 at 12:14, Dave Chinner wrote: > > OK, so the "possible irq lock inversion dependency detected" is a lockdep > > regression, as you explained in the xfs-list thread. What about the > > "RECLAIM_FS-safe -> RECLAIM_FS-unsafe lock order detected" warning - I > > haven't seen it again though, only once with 3.14.0-rc2. > > That was also an i_lock/mmapsem issue, so it's likely to be the same > root cause. I'm testing a fix for it at the moment. Understood. Thanks for looking into this. Christian. -- BOFH excuse #129: The ring needs another token -- 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: email@kvack.org