Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760418Ab2EIRNw (ORCPT ); Wed, 9 May 2012 13:13:52 -0400 Received: from mail-yx0-f174.google.com ([209.85.213.174]:37869 "EHLO mail-yx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758456Ab2EIRNu convert rfc822-to-8bit (ORCPT ); Wed, 9 May 2012 13:13:50 -0400 MIME-Version: 1.0 In-Reply-To: <20120509163732.GN22082@ZenIV.linux.org.uk> References: <1336577114.3638.23.camel@lappy> <20120509161203.GK22082@ZenIV.linux.org.uk> <20120509162854.GM22082@ZenIV.linux.org.uk> <20120509163732.GN22082@ZenIV.linux.org.uk> From: Sasha Levin Date: Wed, 9 May 2012 19:13:29 +0200 Message-ID: Subject: Re: vfs: INFO: possible circular locking dependency detected To: Al Viro Cc: linux-fsdevel@vger.kernel.org, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 900 Lines: 20 On Wed, May 9, 2012 at 6:37 PM, Al Viro wrote: > 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 one" is > not too terrible. ?If that's something else, though, we might have a real > problem... That's probably the case. The proc file got chmodded and exec'ed. Can we do something to eliminate this false positive though? I can't think of anything nice... btw, I've never seen this issue before, even though I run same tests for a while now. What could have triggered it now? -- 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/