linux-kernel - tty OOPS (Re: 2.6.21-rc5-mm2)

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:	Wed, 28 Mar 2007 20:04:46 +0200
From:	Andreas Mohr <andi@...x01.fht-esslingen.de>
To:	Andreas Mohr <andi@...x01.fht-esslingen.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: tty OOPS (Re: 2.6.21-rc5-mm2)

Hi,

[unrelated maintainers removed, Alexey added]

On Wed, Mar 28, 2007 at 07:45:24PM +0200, Andreas Mohr wrote:
> Hi,
> 
> just wanted to add that when analyzing the backtrace I found the comment
> at drivers/char/vt.c/con_close() to be VERY suspicious...
> (need to take tty_mutex to prevent concurrent thread tty access).
> This might just be what happened here despite trying to protect against it.

OK, can we assume that one of

+protect-tty-drivers-list-with-tty_mutex.patch
+tty-minor-merge-correction.patch
+tty-in-tiocsctty-when-we-steal-a-tty-hang-it-up-fix.patch

is responsible / not implemented fully?

Andreas Mohr
-
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/