From: syzbot <syzbot+8c0dbf8843bb75efaa05@syzkaller.appspotmail.com>
To: gustavo@padovan.org, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
marcel@holtmann.org, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, vdronov@redhat.com,
ytkim@qca.qualcomm.com
Subject: Re: general protection fault in qca_setup
Date: Thu, 07 Nov 2019 05:42:08 -0800 [thread overview]
Message-ID: <000000000000eac5200596c1d46b@google.com> (raw)
In-Reply-To: <0000000000002996510581a1487e@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=1436b32c600000
start commit: d1393711 Linux 5.0-rc6
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ee434566c893c7b1
dashboard link: https://syzkaller.appspot.com/bug?extid=8c0dbf8843bb75efaa05
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=130894af400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10799004c00000
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-11-07 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 17:03 general protection fault in qca_setup syzbot
2019-03-17 10:43 ` syzbot
2019-11-07 13:42 ` syzbot [this message]
2019-11-08 8:53 ` 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=000000000000eac5200596c1d46b@google.com \
--to=syzbot+8c0dbf8843bb75efaa05@syzkaller.appspotmail.com \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=vdronov@redhat.com \
--cc=ytkim@qca.qualcomm.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.