From: Peter Hurley <peter@hurleysoftware.com>
To: Peter Hurley <peter@hurleysoftware.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Mikael Pettersson <mikpelinux@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-serial@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] n_tty: Ensure reader restarts worker for next reader
Date: Thu, 07 Nov 2013 15:01:57 -0500 [thread overview]
Message-ID: <527BF1B5.20803@hurleysoftware.com> (raw)
In-Reply-To: <1383850796-24300-1-git-send-email-peter@hurleysoftware.com>
On 11/07/2013 01:59 PM, Peter Hurley wrote:
> A departing reader must restart a flush_to_ldisc() worker _before_
> the next reader enters the read loop; this is to avoid the new reader
> concluding no more i/o is available and prematurely exiting, when the
> old reader simply hasn't re-started the worker yet.
>
> Cc: stable@kernel.org # 3.12
> Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Greg,
I fluffed the stable cc: Please pick this up for 3.12.1.
Regards,
Peter Hurley
next prev parent reply other threads:[~2013-11-07 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 17:34 [GIT PATCH] TTY/Serial fixes for 3.12-rc4 Greg KH
2013-10-05 18:53 ` Linus Torvalds
2013-10-05 23:57 ` Peter Hurley
2013-10-06 2:11 ` Peter Hurley
2013-10-17 21:12 ` Greg KH
2013-10-23 13:16 ` Peter Hurley
2013-11-07 18:59 ` [PATCH] n_tty: Ensure reader restarts worker for next reader Peter Hurley
2013-11-07 20:01 ` Peter Hurley [this message]
2013-11-20 0:21 ` Linus Torvalds
2013-11-20 0:30 ` Greg Kroah-Hartman
2013-11-20 0:43 ` Linus Torvalds
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=527BF1B5.20803@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mikpelinux@gmail.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).