From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Jones Subject: Re: vfs: INFO: possible circular locking dependency detected Date: Wed, 9 May 2012 14:49:09 -0400 Message-ID: <20120509184909.GA27705@redhat.com> References: <1336577114.3638.23.camel@lappy> <20120509161203.GK22082@ZenIV.linux.org.uk> <20120509162854.GM22082@ZenIV.linux.org.uk> <20120509163732.GN22082@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Al Viro , linux-fsdevel@vger.kernel.org, "linux-kernel@vger.kernel.org" To: Sasha Levin Return-path: Received: from mx1.redhat.com ([209.132.183.28]:9841 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752730Ab2EIStN (ORCPT ); Wed, 9 May 2012 14:49:13 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, May 09, 2012 at 07:13:29PM +0200, Sasha Levin wrote: > On Wed, May 9, 2012 at 6:37 PM, Al Viro wr= ote: > > If that's _all_ that happened, I'm not particulary > > concerned; it's not pretty, but saying "thou shalt not grab ->cred= _guard_mutex > > anywhere in ->read() on anything that has exec bits or might get o= ne" is > > not too terrible. =A0If that's something else, though, we might ha= ve a real > > problem... >=20 > That's probably the case. The proc file got chmodded and exec'ed. >=20 > Can we do something to eliminate this false positive though? I can't > think of anything nice... >=20 > btw, > I've never seen this issue before, even though I run same tests for = a > while now. What could have triggered it now? Assuming you're running trinity du-jour, I only added fuzzing of execve= yesterday. Dave -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html