linux-kernel - Re: Linus GIT - INFO: possible circular locking dependency detected

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111109001723.GA26225@kroah.com>
Date:	Tue, 8 Nov 2011 16:17:23 -0800
From:	Greg KH <greg@...ah.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Vasiliy Kulikov <segoon@...nwall.com>,
	Luis Henriques <henrix@...andro.org>,
	Miles Lane <miles.lane@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Alexey Dobriyan <adobriyan@...il.com>, stable@...r.kernel.org
Subject: Re: Linus GIT - INFO: possible circular locking dependency detected

On Tue, Nov 08, 2011 at 03:57:16PM -0800, Andrew Morton wrote:
> On Sat, 5 Nov 2011 13:31:46 +0400
> Vasiliy Kulikov <segoon@...nwall.com> wrote:
> 
> > (cc'ed Andrew and Alexey)
> > 
> > On Thu, Nov 03, 2011 at 20:49 +0000, Luis Henriques wrote:
> > > On Thu, Nov 03, 2011 at 11:57:20AM -0400, Miles Lane wrote:
> > > ...
> > > 
> > > I'm hitting the exact same problem, using a minimal .config file (can send
> > > it if required), by just running "find /".
> > > 
> > > I have bisected the problem and found that commit
> > > aa6afca5bcaba8101f3ea09d5c3e4100b2b9f0e5 seems to be the cause of it.
> 
> Well, let's tell the -stable maintainer(s?)

It's just me.  And my script-bots, but they are all controlled by me in
the end.  Hopefully....

> that aa6afca5bca ("proc:
> fix races against execve() of /proc/PID/fd**") is known to cause a
> regression.

Ok, I'll go delete it from the stable queues for now.

Vasiliy, please let me know when this gets fixed, what the fixed commit
id is, and what this original commit id was, so I can then queue them up
for the stable releases.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/