From: syzbot <syzbot+fe5ea83cdd7fc263f452@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] kernel panic: kernel: panic_on_warn set ... (3)
Date: Sun, 30 Aug 2026 19:02:05 -0700 [thread overview]
Message-ID: <6a94e09d.a8e469d2.cbf3.5611.GAE@google.com> (raw)
In-Reply-To: <20260830225812.1943-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in hci_conn_drop
------------[ cut here ]------------
cnt < 0
WARNING: ./include/net/bluetooth/hci_core.h:1709 at hci_conn_drop+0x1c5/0x2d0 include/net/bluetooth/hci_core.h:1709, CPU#1: kworker/u9:1/4935
Modules linked in:
CPU: 1 UID: 0 PID: 4935 Comm: kworker/u9:1 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: hci3 hci_cmd_sync_work
RIP: 0010:hci_conn_drop+0x1c5/0x2d0 include/net/bluetooth/hci_core.h:1709
Code: e7 e8 9f 49 4f f7 49 8b 34 24 bf 08 00 00 00 4c 89 fa 4c 89 f1 5b 41 5c 41 5d 41 5e 41 5f 5d e9 c1 08 a6 f6 e8 0c 80 df f6 90 <0f> 0b 90 e9 91 fe ff ff 44 89 f1 80 e1 07 38 c1 0f 8c b5 fe ff ff
RSP: 0018:ffffc9000f9f7a10 EFLAGS: 00010293
RAX: ffffffff8ae836a4 RBX: ffff88807fd9c000 RCX: ffff888033f63e80
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000
RBP: 00000000ffffff92 R08: ffff88807fd9c013 R09: 1ffff1100ffb3802
R10: dffffc0000000000 R11: ffffed100ffb3803 R12: ffff88803255ea18
R13: 1ffff110064abd43 R14: 00000000ffffffff R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff888124dda000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3acee37008 CR3: 000000007b2ae000 CR4: 00000000003526f0
Call Trace:
<TASK>
le_read_features_complete+0x24/0xd0 net/bluetooth/hci_sync.c:7873
hci_cmd_sync_work+0x25a/0x3f0 net/bluetooth/hci_sync.c:334
process_one_work kernel/workqueue.c:3387 [inline]
process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3470
worker_thread+0xa47/0xfb0 kernel/workqueue.c:3551
kthread+0x38b/0x480 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Tested on:
commit: cee9395a Linux 7.3-rc1
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12f2ec15580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5e4e3a0e188a497e
dashboard link: https://syzkaller.appspot.com/bug?extid=fe5ea83cdd7fc263f452
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=145a5379580000
prev parent reply other threads:[~2026-08-31 2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 0:09 [syzbot] [nfc?] " syzbot
2026-08-30 17:38 ` [syzbot] [bluetooth?] " syzbot
2026-08-30 22:58 ` Hillf Danton
2026-08-31 2:02 ` 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=6a94e09d.a8e469d2.cbf3.5611.GAE@google.com \
--to=syzbot+fe5ea83cdd7fc263f452@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®