From: Josef Bacik <jbacik@fb.com>
To: Peter Hurley <peter@hurleysoftware.com>,
gregkh@linuxfoundation.org, jslaby@suse.com,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: flush ldisc after hangup
Date: Tue, 1 Mar 2016 14:04:12 -0500 [thread overview]
Message-ID: <56D5E7AC.9040405@fb.com> (raw)
In-Reply-To: <56D5E714.7030900@hurleysoftware.com>
On 03/01/2016 02:01 PM, Peter Hurley wrote:
> On 03/01/2016 10:21 AM, Josef Bacik wrote:
>> On 03/01/2016 01:17 PM, Peter Hurley wrote:
>
>>> Yeah, the race is that the ldisc should not be attempting i/o to
>>> the driver at all. This problem is fixed in -next already, but in
>>> the tty core rather than in each individual tty driver.
>>>
>>
>> Great! Which patch/patches fix this? I looked at linux-next and
>> there's a lot of refactoring stuff, do I need all the things or is
>> there a specific one that fixes this problem? Thanks,
>
> The series that fixes this design problem introduce in 3.10 are these
> patches:
>
> staging: digi: Replace open-coded tty_wakeup()
> serial: 68328: Remove bogus ldisc reset
> bluetooth: hci_ldisc: Remove dead code
> NFC: nci: Remove dead code
> tty: Remove chars_in_buffer() line discipline method
> tty: Fix unsafe ldisc reference via ioctl(TIOCGETD)
> n_tty: Fix unsafe reference to "other" ldisc
> tty: Reset c_line from driver's init_termios
> staging/speakup: Use tty_ldisc_ref() for paste kworker
> tty: Fix comments for tty_ldisc_get()
> tty: Fix comments for tty_ldisc_release()
> tty: Prepare for destroying line discipline on hangup
> tty: Handle NULL tty->ldisc
> tty: Move tty_ldisc_kill()
> tty: Use 'disc' for line discipline index name
> tty: Refactor tty_ldisc_reinit() for reuse
> tty: Destroy ldisc instance on hangup
>
> 'tty: Fix unsafe ldisc reference via ioctl(TIOCGETD)' and
> 'tty: Fix unsafe reference to "other" ldisc' have already
> made their way to most stable trees, afaict.
>
> I doubt I'll submit any more of this series for stable;
> it's just too invasive. I'll probably do it per-driver, like
> your patch. Just an fyi.
>
That's fine, we aren't afraid to pull back lots of stuff to our kernels,
as long as they are destined for upstream. Thanks for the help!
Josef
WARNING: multiple messages have this Message-ID (diff)
From: Josef Bacik <jbacik@fb.com>
To: Peter Hurley <peter@hurleysoftware.com>,
<gregkh@linuxfoundation.org>, <jslaby@suse.com>,
<linux-serial@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial: flush ldisc after hangup
Date: Tue, 1 Mar 2016 14:04:12 -0500 [thread overview]
Message-ID: <56D5E7AC.9040405@fb.com> (raw)
In-Reply-To: <56D5E714.7030900@hurleysoftware.com>
On 03/01/2016 02:01 PM, Peter Hurley wrote:
> On 03/01/2016 10:21 AM, Josef Bacik wrote:
>> On 03/01/2016 01:17 PM, Peter Hurley wrote:
>
>>> Yeah, the race is that the ldisc should not be attempting i/o to
>>> the driver at all. This problem is fixed in -next already, but in
>>> the tty core rather than in each individual tty driver.
>>>
>>
>> Great! Which patch/patches fix this? I looked at linux-next and
>> there's a lot of refactoring stuff, do I need all the things or is
>> there a specific one that fixes this problem? Thanks,
>
> The series that fixes this design problem introduce in 3.10 are these
> patches:
>
> staging: digi: Replace open-coded tty_wakeup()
> serial: 68328: Remove bogus ldisc reset
> bluetooth: hci_ldisc: Remove dead code
> NFC: nci: Remove dead code
> tty: Remove chars_in_buffer() line discipline method
> tty: Fix unsafe ldisc reference via ioctl(TIOCGETD)
> n_tty: Fix unsafe reference to "other" ldisc
> tty: Reset c_line from driver's init_termios
> staging/speakup: Use tty_ldisc_ref() for paste kworker
> tty: Fix comments for tty_ldisc_get()
> tty: Fix comments for tty_ldisc_release()
> tty: Prepare for destroying line discipline on hangup
> tty: Handle NULL tty->ldisc
> tty: Move tty_ldisc_kill()
> tty: Use 'disc' for line discipline index name
> tty: Refactor tty_ldisc_reinit() for reuse
> tty: Destroy ldisc instance on hangup
>
> 'tty: Fix unsafe ldisc reference via ioctl(TIOCGETD)' and
> 'tty: Fix unsafe reference to "other" ldisc' have already
> made their way to most stable trees, afaict.
>
> I doubt I'll submit any more of this series for stable;
> it's just too invasive. I'll probably do it per-driver, like
> your patch. Just an fyi.
>
That's fine, we aren't afraid to pull back lots of stuff to our kernels,
as long as they are destined for upstream. Thanks for the help!
Josef
next prev parent reply other threads:[~2016-03-01 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 18:02 [PATCH] serial: flush ldisc after hangup Josef Bacik
2016-03-01 18:02 ` Josef Bacik
2016-03-01 18:17 ` Peter Hurley
2016-03-01 18:21 ` Josef Bacik
2016-03-01 18:21 ` Josef Bacik
2016-03-01 19:01 ` Peter Hurley
2016-03-01 19:04 ` Josef Bacik [this message]
2016-03-01 19:04 ` Josef Bacik
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=56D5E7AC.9040405@fb.com \
--to=jbacik@fb.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.