From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] bce86b: adapter: remove the devices from the list before f...
Date: Fri, 18 Sep 2026 15:25:27 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1169029/000000-bce86b@github.com> (raw)
Branch: refs/heads/1169029
Home: https://github.com/bluez/bluez
Commit: bce86bc9645e31c6c20b9e2d58337cbdec689811
https://github.com/bluez/bluez/commit/bce86bc9645e31c6c20b9e2d58337cbdec689811
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-09-18 (Fri, 18 Sep 2026)
Changed paths:
M src/adapter.c
Log Message:
-----------
adapter: remove the devices from the list before freeing them
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
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-18 22:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1169029/000000-bce86b@github.com \
--to=noreply@github.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 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.