linux-kernel - Re: [GIT PATCH] TTY patches for 3.7-rc1

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]

Message-ID: <506A0FCA.2020908@suse.cz>
Date:	Mon, 01 Oct 2012 23:48:58 +0200
From:	Jiri Slaby <jslaby@...e.cz>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
	linux-serial@...r.kernel.org, Stanislav Kozina <skozina@...hat.com>
Subject: Re: [GIT PATCH] TTY patches for 3.7-rc1

On 10/01/2012 08:30 PM, Greg KH wrote:
> Stanislav Kozina (2):
>       tty: Fix possible race in n_tty_read()

The (pretty hopeless) commit log says:
    Fix possible panic caused by unlocked access to tty->read_cnt in
    while-loop condition in n_tty_read().

Just curious, what kind of panic that can cause, can you be more
concrete on that? I suppose two readers, one eats everything, the other
is a killer? And should we backport to -stable?

thanks,
-- 
js
suse labs
--
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/