From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: bug in tty ldisc and friends
Date: Tue, 16 Jun 2009 09:37:41 +0100 [thread overview]
Message-ID: <20090616093741.0d5b36bc@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.0906160144340.26673@gandalf.stny.rr.com>
On Tue, 16 Jun 2009 01:45:36 -0400 (EDT)
Steven Rostedt <rostedt@goodmis.org> wrote:
>
> [ Ingo and Andrew, sorry for the repost, but I forgot to Cc LKML and I
> also used Alan's old email. ]
>
> I can easily trigger a bug in the tty code by enabling the event tracers.
Yes I know. I sent Linus a temporary workaround yesterday. The bug is as
old as the hills (the race in various forms predates any git or bk
history!). The ldisc changes happened to make it more visible.
Unfortunately its non trivial to fix but the workaround should make it as
hard to hit now as in 2.6.30 while I sort the funnies out. Really though
I need the lock verifier working to do that, and its been busted since
2.6.30 8(
Alan
next prev parent reply other threads:[~2009-06-16 8:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 5:45 Steven Rostedt
2009-06-16 8:37 ` Alan Cox [this message]
2009-06-16 8:50 ` Ingo Molnar
2009-06-16 8:57 ` Alan Cox
2009-06-16 9:09 ` Ingo Molnar
2009-06-16 10:00 ` Ingo Molnar
2009-06-16 10:04 ` Alan Cox
2009-06-16 10:12 ` Ingo Molnar
2009-06-16 10:25 ` Ingo Molnar
2009-06-16 10:29 ` Ingo Molnar
2009-06-16 10:34 ` Joerg Roedel
2009-06-16 10:45 ` Ingo Molnar
2009-06-16 10:36 ` Ingo Molnar
2009-06-16 11:39 ` Joerg Roedel
2009-06-16 12:11 ` Ingo Molnar
2009-06-16 15:24 ` Joerg Roedel
2009-06-17 8:32 ` Peter Zijlstra
2009-06-17 14:10 ` Ingo Molnar
2009-06-17 14:28 ` Joerg Roedel
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=20090616093741.0d5b36bc@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®