linux-kernel - Re: bug in tty ldisc and friends

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]

Date:	Tue, 16 Jun 2009 09:37:41 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: bug in tty ldisc and friends

On Tue, 16 Jun 2009 01:45:36 -0400 (EDT)
Steven Rostedt <rostedt@...dmis.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
--
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/