[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0912120915390.3526@localhost.localdomain>
Date: Sat, 12 Dec 2009 09:16:43 -0800 (PST)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andrew Morton <akpm@...ux-foundation.org>
cc: Ingo Molnar <mingo@...e.hu>, Greg KH <gregkh@...e.de>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] TTY patches for 2.6.33-git
On Sat, 12 Dec 2009, Andrew Morton wrote:
> On Sat, 12 Dec 2009 11:10:32 +0100 Ingo Molnar <mingo@...e.hu> wrote:
>
> >
> > * Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > > Seems to be quite .config-dependent.
> >
> > My theory is that it's a race and that it's thus timing dependent. TTY
> > SMP details get stressed most during a particular point during bootup,
> > when all the mingetty's are starting up all at once and race with each
> > other.
> >
> > If you are lucky to not hit the bug then, then the likelyhood is much
> > lower later on.
> >
> > It would be nice if Alan posted his TTY stress-testing code. It could
> > potentially make this bug bisectable.
> >
>
> I'm surprised that lockdep didn't notice that ab/ba I thought I saw.
> Maybe the do_tty_hangup()->tty_fasync() never happens.
The kernel lock cannot have any ABBA deadlocks.
If somebody blocks on another lock (after getting the kernel lock), the
kernel lock will be dropped. So no ABBA.
Linus
--
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/
Powered by blists - more mailing lists