From: syzbot <syzbot+a950165cbb86bdd023a4@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, gustavo@padovan.org,
johan.hedberg@gmail.com, jslaby@suse.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
loic.poulain@intel.com, marcel@holtmann.org, mhjungk@gmail.com,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
vdronov@redhat.com
Subject: Re: WARNING in tty_set_termios
Date: Sun, 08 Dec 2019 22:20:01 -0800 [thread overview]
Message-ID: <000000000000b17fae05993f628b@google.com> (raw)
In-Reply-To: <000000000000bcd434057f4eb905@google.com>
syzbot suspects this bug was fixed by commit:
commit b36a1552d7319bbfd5cf7f08726c23c5c66d4f73
Author: Vladis Dronov <vdronov@redhat.com>
Date: Tue Jul 30 09:33:45 2019 +0000
Bluetooth: hci_uart: check for missing tty operations
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10b20aeae00000
start commit: 66c56cfa Merge tag 'remove-dma_zalloc_coherent-5.0' of git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=b05cfdb4ee8ab9b2
dashboard link: https://syzkaller.appspot.com/bug?extid=a950165cbb86bdd023a4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=121cee07400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16fdaed8c00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: Bluetooth: hci_uart: check for missing tty operations
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-12-09 6:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000bcd434057f4eb905@google.com>
2019-03-17 15:15 ` WARNING in tty_set_termios syzbot
2019-12-09 6:20 ` syzbot [this message]
2019-12-12 15:57 ` Vladis Dronov
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=000000000000b17fae05993f628b@google.com \
--to=syzbot+a950165cbb86bdd023a4@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=jslaby@suse.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@intel.com \
--cc=marcel@holtmann.org \
--cc=mhjungk@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=vdronov@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).