public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b170dbf55520ebf5969a@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: Re: [syzbot] [bluetooth?] WARNING: ODEBUG bug in hci_release_dev (2)
Date: Tue, 17 Mar 2026 08:12:21 -0700	[thread overview]
Message-ID: <69b96f55.050a0220.248e02.012e.GAE@google.com> (raw)
In-Reply-To: <000000000000cd69c7061dfe35d2@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: Re: [syzbot] [bluetooth?] WARNING: ODEBUG bug in hci_release_dev (2)
Author: abysamross@gmail.com

#syz test

======================================================================

From 006a3d0d3cc1b5e7be6d4eec2cbafacdbd40816c Mon Sep 17 00:00:00 2001
From: Aby Sam Ross <abysamross@gmail.com>
Date: Tue, 17 Mar 2026 00:21:32 +0530
Subject: [PATCH v1 1/1] Bluetooth: hci_release_dev: cancel coredump work

The hci device's coredump timeout work remains active when the memory
associated with the hci device is freed up in hci_release_dev(), causing
an active object to be freed.
Cancel all hci coredump related work while in hci_release_dev().

Signed-off-by: Aby Sam Ross <abysamross@gmail.com>
---
 include/net/bluetooth/coredump.h | 3 +++
 net/bluetooth/coredump.c         | 7 +++++++
 net/bluetooth/hci_core.c         | 1 +
 3 files changed, 11 insertions(+)

diff --git a/include/net/bluetooth/coredump.h b/include/net/bluetooth/coredump.h
index 72f51b587a04..18318a1f8e1a 100644
--- a/include/net/bluetooth/coredump.h
+++ b/include/net/bluetooth/coredump.h
@@ -71,6 +71,7 @@ int hci_devcd_append(struct hci_dev *hdev, struct sk_buff *skb);
 int hci_devcd_append_pattern(struct hci_dev *hdev, u8 pattern, u32 len);
 int hci_devcd_complete(struct hci_dev *hdev);
 int hci_devcd_abort(struct hci_dev *hdev);
+void hci_devcd_cancel_work_sync(struct hci_dev *hdev);
 
 #else
 
@@ -111,6 +112,8 @@ static inline int hci_devcd_abort(struct hci_dev *hdev)
 	return -EOPNOTSUPP;
 }
 
+static inline void hci_devcd_cancel_work_sync(struct hci_dev *hdev) {}
+
 #endif /* CONFIG_DEV_COREDUMP */
 
 #endif /* __COREDUMP_H */
diff --git a/net/bluetooth/coredump.c b/net/bluetooth/coredump.c
index 720cb79adf96..e3b65d627019 100644
--- a/net/bluetooth/coredump.c
+++ b/net/bluetooth/coredump.c
@@ -84,6 +84,13 @@ static void hci_devcd_notify(struct hci_dev *hdev, int state)
 		hdev->dump.notify_change(hdev, state);
 }
 
+
+void hci_devcd_cancel_work_sync(struct hci_dev *hdev)
+{
+    cancel_work_sync(&hdev->dump.dump_rx);
+    cancel_delayed_work_sync(&hdev->dump.dump_timeout);
+}
+
 /* Call with hci_dev_lock only. */
 void hci_devcd_reset(struct hci_dev *hdev)
 {
diff --git a/net/bluetooth/hci_core.c b/net/bluetooth/hci_core.c
index 31308c1de4ec..95416cd0d580 100644
--- a/net/bluetooth/hci_core.c
+++ b/net/bluetooth/hci_core.c
@@ -2749,6 +2749,7 @@ void hci_release_dev(struct hci_dev *hdev)
 
 	destroy_workqueue(hdev->workqueue);
 	destroy_workqueue(hdev->req_workqueue);
+    hci_devcd_cancel_work_sync(hdev);
 
 	hci_dev_lock(hdev);
 	hci_bdaddr_list_clear(&hdev->reject_list);
-- 
2.53.0


  parent reply	other threads:[~2026-03-17 15:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 13:25 [syzbot] [bluetooth?] WARNING: ODEBUG bug in hci_release_dev (2) syzbot
2024-10-14 23:11 ` syzbot
2024-12-21 14:19 ` syzbot
2026-03-16 16:07 ` Forwarded: " syzbot
2026-03-17 15:12 ` syzbot [this message]
2026-03-21 10:49 ` Forwarded: test syzbot+b170dbf55520ebf5969a syzbot
2026-03-21 11:28 ` Forwarded: test fix for syzbot+b170dbf55520ebf5969a 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=69b96f55.050a0220.248e02.012e.GAE@google.com \
    --to=syzbot+b170dbf55520ebf5969a@syzkaller.appspotmail.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