Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752907AbaBQXDr (ORCPT ); Mon, 17 Feb 2014 18:03:47 -0500 Received: from slmp-550-94.slc.westdc.net ([50.115.112.57]:52719 "EHLO slmp-550-94.slc.westdc.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1750939AbaBQXDq convert rfc822-to-8bit (ORCPT ); Mon, 17 Feb 2014 18:03:46 -0500 X-Greylist: delayed 2947 seconds by postgrey-1.27 at vger.kernel.org; Mon, 17 Feb 2014 18:03:46 EST Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: btrfs "possible irq lock inversion dependency detected" From: Chris Murphy In-Reply-To: <20140217200951.GB20312@optiplex> Date: Mon, 17 Feb 2014 15:14:34 -0700 Cc: Chris Mason , Josef Bacik , linux-btrfs@vger.kernel.org, Dave Jones , trinity@vger.kernel.org, linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8BIT Message-Id: <4F3CC8F0-C37E-4448-AF65-796E643A301B@colorremedies.com> References: <20140217200951.GB20312@optiplex> To: Tommi Rantala X-Mailer: Apple Mail (2.1510) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - slmp-550-94.slc.westdc.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - colorremedies.com X-Get-Message-Sender-Via: slmp-550-94.slc.westdc.net: authenticated_id: whatever@colorremedies.com X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Feb 17, 2014, at 1:09 PM, Tommi Rantala wrote: > Hello, > > Saw this while fuzzing the kernel with Trinity. > > Tommi > > > [ 396.136048] ========================================================= > [ 396.136048] [ INFO: possible irq lock inversion dependency detected ] > [ 396.136048] 3.14.0-rc3 #1 Not tainted > [ 396.136048] --------------------------------------------------------- > [ 396.136048] kswapd0/1482 just changed the state of lock: > [ 396.136048] (&delayed_node->mutex){+.+.-.}, at: [] __btrfs_release_delayed_node+0x4b/0x1e0 > [ 396.136048] but this lock took another, RECLAIM_FS-unsafe lock in the past: > [ 396.136048] (&found->groups_sem){+++++.} Looks like this is the same thing previously report on Btrfs list with 3.14.0-rc1 here: https://bugzilla.redhat.com/show_bug.cgi?id=1062439 Which points to this: https://bugzilla.redhat.com/show_bug.cgi?id=1062833#c24 Which points to this patch: http://marc.info/?l=linux-netdev&m=139233546723342&q=raw Chris Murphy-- 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/