From: syzbot <syzbot+d6282a21a27259b5f7e7@syzkaller.appspotmail.com>
To: eadavis@qq.com, hdanton@sina.com, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
marcel@holtmann.org, mukattreyee@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] WARNING in hci_conn_set_handle
Date: Thu, 25 Jul 2024 16:45:03 -0700 [thread overview]
Message-ID: <000000000000d390be061e1afb9c@google.com> (raw)
In-Reply-To: <000000000000ec64cd0616084ae9@google.com>
syzbot suspects this issue was fixed by commit:
commit 015d79c96d62cd8a4a359fcf5be40d58088c936b
Author: Edward Adam Davis <eadavis@qq.com>
Date: Mon Jun 17 11:09:37 2024 +0000
Bluetooth: Ignore too large handle values in BIG
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13110dad980000
start commit: 480e035fc4c7 Merge tag 'drm-next-2024-03-13' of https://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1e5b814e91787669
dashboard link: https://syzkaller.appspot.com/bug?extid=d6282a21a27259b5f7e7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10f3e213180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=162d4723180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: Ignore too large handle values in BIG
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-07-25 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 6:05 [syzbot] [bluetooth?] WARNING in hci_conn_set_handle syzbot
2024-04-14 8:30 ` Hillf Danton
2024-04-14 8:58 ` syzbot
2024-04-15 9:33 ` [syzbot] test syzbot
2024-07-25 23:45 ` syzbot [this message]
[not found] <CA+LQOUczHtC_3cxUFbkcpWYwLCr62k229ym9B3NL6RS6NQHdhw@mail.gmail.com>
2024-04-15 13:07 ` [syzbot] [bluetooth?] WARNING in hci_conn_set_handle syzbot
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=000000000000d390be061e1afb9c@google.com \
--to=syzbot+d6282a21a27259b5f7e7@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=hdanton@sina.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=mukattreyee@gmail.com \
--cc=syzkaller-bugs@googlegroups.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