From: syzbot <syzbot+ce27f6f75880d7fe265c@syzkaller.appspotmail.com>
To: avkrasnov@salutedevices.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
luiz.von.dentz@intel.com, marcel@holtmann.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] general protection fault in h5_close
Date: Thu, 20 Feb 2025 17:01:03 -0800 [thread overview]
Message-ID: <67b7d04f.050a0220.14d86d.0303.GAE@google.com> (raw)
In-Reply-To: <67b75955.050a0220.14d86d.02e5.GAE@google.com>
syzbot has bisected this issue to:
commit 3ca66179e56d25f1e3ed1608241abb487c63e9b7
Author: Arseniy Krasnov <avkrasnov@salutedevices.com>
Date: Thu Jan 30 18:43:26 2025 +0000
Bluetooth: hci_uart: fix race during initialization
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=102567f8580000
start commit: e5d3fd687aac Add linux-next specific files for 20250218
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=122567f8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=142567f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4e945b2fe8e5992f
dashboard link: https://syzkaller.appspot.com/bug?extid=ce27f6f75880d7fe265c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=178f2ba4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=123375b0580000
Reported-by: syzbot+ce27f6f75880d7fe265c@syzkaller.appspotmail.com
Fixes: 3ca66179e56d ("Bluetooth: hci_uart: fix race during initialization")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-02-21 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 16:33 [syzbot] [bluetooth?] general protection fault in h5_close syzbot
2025-02-21 1:01 ` syzbot [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=67b7d04f.050a0220.14d86d.0303.GAE@google.com \
--to=syzbot+ce27f6f75880d7fe265c@syzkaller.appspotmail.com \
--cc=avkrasnov@salutedevices.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=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 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.