From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v1] adapter: remove the devices from the list before freeing them
Date: Fri, 18 Sep 2026 17:59:15 -0400 [thread overview]
Message-ID: <20260918215915.2572126-1-luiz.dentz@gmail.com> (raw)
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
The devices of an adapter are freed one by one when it is removed, but
the list keeps pointing at them until every one of them is gone, so it
refers to freed devices while the remaining ones are being removed.
Freeing a device looks devices up though, e.g. cleaning up its GATT
server reports the disconnection, which searches the list for the
device it belongs to, and the search reads the devices already freed:
ERROR: AddressSanitizer: heap-use-after-free
in bacmp lib/bluetooth/bluetooth.h:438
in device_addr_type_cmp src/device.c:5657
in btd_adapter_find_device src/adapter.c:1055
in att_disconnected src/gatt-database.c:335
in gatt_server_cleanup src/device.c:842
in device_free src/device.c:918
Take each device out of the list before removing it, so only the ones
still to be removed are ever found.
This needs more than one device on the adapter to show up, which the
test of a coordinated set is the first to leave behind.
Assisted-by: opencode:claude-opus-5
---
src/adapter.c | 19 ++++++++++++-------
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/src/adapter.c b/src/adapter.c
index 717db2ea9bfe..50b4dc6d724e 100644
--- a/src/adapter.c
+++ b/src/adapter.c
@@ -7293,7 +7293,6 @@ static struct btd_adapter *btd_adapter_new(uint16_t index)
static void adapter_remove(struct btd_adapter *adapter)
{
- GSList *l;
struct gatt_db *db;
struct btd_ranging_provider_manager *ranging_manager;
@@ -7302,13 +7301,19 @@ static void adapter_remove(struct btd_adapter *adapter)
g_slist_free(adapter->connect_list);
adapter->connect_list = NULL;
- for (l = adapter->devices; l; l = l->next) {
- device_removed_drivers(adapter, l->data);
- device_remove(l->data, FALSE);
- }
+ while (adapter->devices) {
+ struct btd_device *device = adapter->devices->data;
- g_slist_free(adapter->devices);
- adapter->devices = NULL;
+ /* Take the device out of the list before removing it, as
+ * freeing it looks devices up, e.g. when cleaning up its
+ * GATT server, and the ones already freed would still be
+ * found.
+ */
+ adapter->devices = g_slist_remove(adapter->devices, device);
+
+ device_removed_drivers(adapter, device);
+ device_remove(device, FALSE);
+ }
g_slist_free(adapter->discovery_found);
adapter->discovery_found = NULL;
--
2.55.0
next reply other threads:[~2026-09-18 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 21:59 Luiz Augusto von Dentz [this message]
2026-09-18 23:23 ` [BlueZ,v1] adapter: remove the devices from the list before freeing them bluez.test.bot
2026-09-21 14:30 ` [PATCH BlueZ v1] " patchwork-bot+bluetooth
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=20260918215915.2572126-1-luiz.dentz@gmail.com \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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