From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+5897b3c764f5989ea942@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] WARNING in hci_connect_sco
Date: Sun, 1 Feb 2026 10:15:55 +0800 [thread overview]
Message-ID: <20260201021556.2474-1-hdanton@sina.com> (raw)
In-Reply-To: <697e08a4.050a0220.16b13.0092.GAE@google.com>
> Date: Sat, 31 Jan 2026 05:50:28 -0800
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: ad9a728a3388 Merge tag 'for-linus-iommufd' of git://git.ke..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15513c5a580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=f1fac0919970b671
> dashboard link: https://syzkaller.appspot.com/bug?extid=5897b3c764f5989ea942
> compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17b45322580000
#syz test
--- x/include/net/bluetooth/hci_core.h
+++ y/include/net/bluetooth/hci_core.h
@@ -1687,6 +1687,7 @@ static inline void hci_conn_drop(struct
if (atomic_dec_and_test(&conn->refcnt)) {
unsigned long timeo;
+ struct hci_dev *hdev;
switch (conn->type) {
case ACL_LINK:
@@ -1707,8 +1708,14 @@ static inline void hci_conn_drop(struct
}
cancel_delayed_work(&conn->disc_work);
- queue_delayed_work(conn->hdev->workqueue,
- &conn->disc_work, timeo);
+ hdev = conn->hdev;
+ rcu_read_lock();
+ if (test_bit(HCI_RESET, &hdev->flags) ||
+ hci_dev_test_flag(hdev, HCI_CMD_DRAIN_WORKQUEUE))
+ ;
+ else
+ queue_delayed_work(hdev->workqueue, &conn->disc_work, timeo);
+ rcu_read_unlock();
}
}
--
next prev parent reply other threads:[~2026-02-01 2:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 2:18 syzbot
2026-01-31 13:50 ` syzbot
2026-02-01 2:15 ` Hillf Danton [this message]
2026-02-01 2:34 ` syzbot
2026-02-02 1:12 ` Hillf Danton
2026-02-02 1:32 ` 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=20260201021556.2474-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+5897b3c764f5989ea942@syzkaller.appspotmail.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
Powered by JetHome