From: Jiri Slaby <jslaby@suse.cz>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Stanislav Kozina <skozina@redhat.com>
Subject: Re: [GIT PATCH] TTY patches for 3.7-rc1
Date: Mon, 01 Oct 2012 23:48:58 +0200 [thread overview]
Message-ID: <506A0FCA.2020908@suse.cz> (raw)
In-Reply-To: <20121001183046.GA13042@kroah.com>
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
next prev parent reply other threads:[~2012-10-01 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 18:30 [GIT PATCH] TTY patches for 3.7-rc1 Greg KH
2012-10-01 21:48 ` Jiri Slaby [this message]
2012-10-01 22:13 ` Greg KH
2012-10-28 10:04 ` Jiri Slaby
2012-10-28 15:22 ` Alan Cox
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=506A0FCA.2020908@suse.cz \
--to=jslaby@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=skozina@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).