From: shuah <shuah@kernel.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
johan@kernel.org, viro@zeniv.linux.org.uk,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
shuah <shuah@kernel.org>
Subject: Re: [PATCH v3] bluetooth: Fix WARNING in tty_set_termios()
Date: Sun, 3 Feb 2019 12:36:32 -0700 [thread overview]
Message-ID: <a758f44b-24e5-6f5f-a809-228a4001f84a@kernel.org> (raw)
In-Reply-To: <0CC28468-8E2F-4DEE-8307-DA0CEA59A8D0@holtmann.org>
On 2/3/19 10:31 AM, Marcel Holtmann wrote:
> Hi Shuah,
>
>> tty_set_termios() has the following WARN_ON which can be triggered with a
>> syscall to invoke TIOCSETD __NR_ioctl.
>>
>> WARN_ON(tty->driver->type == TTY_DRIVER_TYPE_PTY &&
>> tty->driver->subtype == PTY_TYPE_MASTER);
>> Reference: https://syzkaller.appspot.com/bug?id=2410d22f1d8e5984217329dd0884b01d99e3e48d
>>
>> Johan Hovold said: "The problemm started with
>> commit 7721383f4199 ("Bluetooth: hci_uart: Support
>> operational speed during setup") which introduced a new way for how
>> tty_set_termios() could end up being called for a master pty."
>>
>> Fix it by by preventing setting the HCI line discipline for PTYs in
>> hci_uart_tty_open(). Looked into keying off of tty and ldisc ops, and
>> couldn't find any that would be conclusive. Checking tty as such clearly
>> tags the reason for rejecting the request to set ldisc.
>>
>> Reported-by: syzbot+a950165cbb86bdd023a4@syzkaller.appspotmail.com
>> Cc: Johan Hovold <johan@kernel.org>
>> Cc: Marcel Holtmann <marcel@holtmann.org>
>> Cc: Al Viro <viro@zeniv.linux.org.uk>
>> Signed-off-by: Shuah Khan <shuah@kernel.org>
>> ---
>> drivers/bluetooth/hci_ldisc.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/bluetooth/hci_ldisc.c b/drivers/bluetooth/hci_ldisc.c
>> index fbf7b4df23ab..a3d313fcc0f2 100644
>> --- a/drivers/bluetooth/hci_ldisc.c
>> +++ b/drivers/bluetooth/hci_ldisc.c
>> @@ -480,6 +480,11 @@ static int hci_uart_tty_open(struct tty_struct *tty)
>> if (tty->ops->write == NULL)
>> return -EOPNOTSUPP;
>>
>> + /* don't set HCI line discipline on PTYs */
>> + if (tty->driver->type == TTY_DRIVER_TYPE_PTY &&
>> + tty->driver->subtype == PTY_TYPE_MASTER)
>> + return -EINVAL;
>> +
>
> this is turning in circles. What is wrong with checking !tty->ops->set_termios here?
Yeah. I looked into set_termios and thought that it is set in this path.
My bad. okay v4 is on its way. Sorry it took so long to get on the same
page with you. :(
thanks,
-- Shuah
prev parent reply other threads:[~2019-02-03 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 16:48 [PATCH v3] bluetooth: Fix WARNING in tty_set_termios() Shuah Khan
2019-02-03 17:31 ` Marcel Holtmann
2019-02-03 19:36 ` shuah [this message]
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=a758f44b-24e5-6f5f-a809-228a4001f84a@kernel.org \
--to=shuah@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=johan@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=viro@zeniv.linux.org.uk \
/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