Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752044AbaBNBWS (ORCPT ); Thu, 13 Feb 2014 20:22:18 -0500 Received: from trent.utfs.org ([94.185.90.103]:45354 "EHLO trent.utfs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751199AbaBNBWR (ORCPT ); Thu, 13 Feb 2014 20:22:17 -0500 Date: Thu, 13 Feb 2014 17:22:06 -0800 (PST) From: Christian Kujau To: Dave Chinner cc: LKML , xfs@oss.sgi.com, linux-mm@kvack.org 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> User-Agent: Alpine 2.19.4 (DEB 40 2013-11-18) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-AV-Checked: ClamAV using ClamSMTP (127.0.0.1) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.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 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/