From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vasiliy Kulikov <segoon@openwall.com>,
Luis Henriques <henrix@camandro.org>,
Miles Lane <miles.lane@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
stable@vger.kernel.org
Subject: Re: Linus GIT - INFO: possible circular locking dependency detected
Date: Tue, 8 Nov 2011 16:40:13 -0800 [thread overview]
Message-ID: <20111109004013.GA30562@kroah.com> (raw)
In-Reply-To: <20111109001723.GA26225@kroah.com>
On Tue, Nov 08, 2011 at 04:17:23PM -0800, Greg KH wrote:
> 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@openwall.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.
Now removed.
next prev parent reply other threads:[~2011-11-09 0:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 15:57 Linus GIT - INFO: possible circular locking dependency detected Miles Lane
2011-11-03 20:49 ` Luis Henriques
2011-11-05 9:31 ` Vasiliy Kulikov
2011-11-08 23:57 ` Andrew Morton
2011-11-09 0:17 ` Greg KH
2011-11-09 0:40 ` Greg KH [this message]
2011-11-09 19:11 ` Luis Henriques
2011-11-09 19:52 ` Peter Zijlstra
2011-11-09 20:05 ` Luis Henriques
2011-11-14 17:27 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111109004013.GA30562@kroah.com \
--to=greg@kroah.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=henrix@camandro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=segoon@openwall.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox