From: Peter Hurley <peter@hurleysoftware.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Mikael Pettersson <mikpelinux@gmail.com>,
Jiri Slaby <jslaby@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org
Subject: Re: [GIT PATCH] TTY/Serial fixes for 3.12-rc4
Date: Wed, 23 Oct 2013 09:16:36 -0400 [thread overview]
Message-ID: <5267CC34.1020700@hurleysoftware.com> (raw)
In-Reply-To: <20131017211236.GA6155@kroah.com>
On 10/17/2013 05:12 PM, Greg KH wrote:
> On Sat, Oct 05, 2013 at 10:11:25PM -0400, Peter Hurley wrote:
>> On 10/05/2013 07:57 PM, Peter Hurley wrote:
>>
>> However, the atomic_read_lock exclusion needs to cover the
>> unconditional n_tty_set_room() when leaving n_tty_read() and
>> it doesn't. Thus, the departing reader fails to ensure the subsequent
>> reader has a running flush_to_ldisc() worker.
>>
>> Patch forthcoming.
>
> Did I miss this patch, or did it not come forth?
Sorry to go off-grid like that; interrupt(life) happened.
I'm testing that patch now.
Regards,
Peter Hurley
next prev parent reply other threads:[~2013-10-23 13:16 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 [this message]
2013-11-07 18:59 ` [PATCH] n_tty: Ensure reader restarts worker for next reader Peter Hurley
2013-11-07 20:01 ` Peter Hurley
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=5267CC34.1020700@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mikpelinux@gmail.com \
--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).