From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v3 2/9] attrib: Fix unregistering notifications registered with bt_gatt_client
Date: Thu, 24 Sep 2026 11:46:24 -0400 [thread overview]
Message-ID: <20260924154631.369299-3-luiz.dentz@gmail.com> (raw)
In-Reply-To: <20260924154631.369299-1-luiz.dentz@gmail.com>
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
g_attrib_register registers ATT_OP_HANDLE_NOTIFY with bt_gatt_client,
when there is one, returning its id, but g_attrib_unregister always
unregisters with bt_att, so the notification was never unregistered
and its destroy callback was called once bt_gatt_client was freed,
after the user data was freed, e.g. the reports of HoG:
ERROR: AddressSanitizer: heap-use-after-free
#11 report_notify_destroy profiles/input/hog-lib.c:359
#12 attrib_callbacks_destroy attrib/gattrib.c:126
#13 notify_data_unref src/shared/gatt-client.c:256
...
#17 bt_gatt_client_free src/shared/gatt-client.c:2293
#18 bt_gatt_client_unref src/shared/gatt-client.c:2605
#19 g_attrib_unref attrib/gattrib.c:154
#20 attio_cleanup src/device.c:874
Give out ids of our own, keeping track of how each one was registered
so it is unregistered accordingly.
---
attrib/gattrib.c | 90 +++++++++++++++++++++++++++++++++---------------
1 file changed, 63 insertions(+), 27 deletions(-)
diff --git a/attrib/gattrib.c b/attrib/gattrib.c
index 3a988e131e94..05a17ba9393f 100644
--- a/attrib/gattrib.c
+++ b/attrib/gattrib.c
@@ -45,6 +45,7 @@ struct _GAttrib {
uint8_t *buf;
int buflen;
struct queue *track_ids;
+ unsigned int next_reg_id;
};
struct attrib_callbacks {
@@ -55,6 +56,9 @@ struct attrib_callbacks {
gpointer user_data;
GAttrib *parent;
uint16_t notify_handle;
+ unsigned int reg_id;
+ unsigned int att_id;
+ unsigned int client_id;
};
GAttrib *g_attrib_new(GIOChannel *io, guint16 mtu, bool ext_signed)
@@ -363,38 +367,52 @@ guint g_attrib_register(GAttrib *attrib, guint8 opcode, guint16 handle,
GAttribNotifyFunc func, gpointer user_data,
GDestroyNotify notify)
{
- struct attrib_callbacks *cb = NULL;
+ struct attrib_callbacks *cb;
if (!attrib)
return 0;
- if (func || notify) {
- cb = new0(struct attrib_callbacks, 1);
- if (!cb)
- return 0;
- cb->notify_func = func;
- cb->notify_handle = handle;
- cb->user_data = user_data;
- cb->destroy_func = notify;
- cb->parent = attrib;
- queue_push_head(attrib->callbacks, cb);
- }
+ cb = new0(struct attrib_callbacks, 1);
+ if (!cb)
+ return 0;
- if (opcode == ATT_OP_HANDLE_NOTIFY && attrib->client) {
- unsigned int id;
+ cb->notify_func = func;
+ cb->notify_handle = handle;
+ cb->user_data = user_data;
+ cb->destroy_func = notify;
+ cb->parent = attrib;
+ queue_push_head(attrib->callbacks, cb);
- id = bt_gatt_client_register_notify(attrib->client, handle,
- NULL, client_notify_cb, cb,
- attrib_callbacks_remove);
- if (id)
- return id;
- }
-
- if (opcode == GATTRIB_ALL_REQS)
- opcode = BT_ATT_ALL_REQUESTS;
-
- return bt_att_register(attrib->att, opcode, attrib_callback_notify,
+ /* The notifications are registered with bt_gatt_client when there
+ * is one, which uses ids of its own, so give out ids of our own to
+ * know how to unregister them.
+ */
+ if (opcode == ATT_OP_HANDLE_NOTIFY && attrib->client)
+ cb->client_id = bt_gatt_client_register_notify(attrib->client,
+ handle, NULL, client_notify_cb,
cb, attrib_callbacks_remove);
+
+ if (!cb->client_id) {
+ if (opcode == GATTRIB_ALL_REQS)
+ opcode = BT_ATT_ALL_REQUESTS;
+
+ cb->att_id = bt_att_register(attrib->att, opcode,
+ attrib_callback_notify, cb,
+ attrib_callbacks_remove);
+ }
+
+ if (!cb->client_id && !cb->att_id) {
+ queue_remove(attrib->callbacks, cb);
+ free(cb);
+ return 0;
+ }
+
+ if (++attrib->next_reg_id == 0)
+ ++attrib->next_reg_id;
+
+ cb->reg_id = attrib->next_reg_id;
+
+ return cb->reg_id;
}
uint8_t *g_attrib_get_buffer(GAttrib *attrib, size_t *len)
@@ -456,12 +474,30 @@ gboolean g_attrib_attach_client(GAttrib *attrib, struct bt_gatt_client *client)
return TRUE;
}
+static bool match_reg_id(const void *data, const void *match_data)
+{
+ const struct attrib_callbacks *cb = data;
+
+ return cb->reg_id && cb->reg_id == PTR_TO_UINT(match_data);
+}
+
gboolean g_attrib_unregister(GAttrib *attrib, guint id)
{
- if (!attrib)
+ struct attrib_callbacks *cb;
+
+ if (!attrib || !id)
return FALSE;
- return bt_att_unregister(attrib->att, id);
+ cb = queue_find(attrib->callbacks, match_reg_id, UINT_TO_PTR(id));
+ if (!cb)
+ return FALSE;
+
+ /* cb is freed by attrib_callbacks_remove once unregistered */
+ if (cb->client_id)
+ return bt_gatt_client_unregister_notify(attrib->client,
+ cb->client_id);
+
+ return bt_att_unregister(attrib->att, cb->att_id);
}
gboolean g_attrib_unregister_all(GAttrib *attrib)
--
2.55.0
next prev parent reply other threads:[~2026-09-24 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 15:46 [PATCH BlueZ v3 0/9] Add HID over GATT functional tests Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 1/9] shared/gatt-client: Fix calling destroy after unregistering notify Luiz Augusto von Dentz
2026-09-24 19:16 ` Add HID over GATT functional tests bluez.test.bot
2026-10-09 19:52 ` bluez.test.bot
2026-09-24 15:46 ` Luiz Augusto von Dentz [this message]
2026-09-24 15:46 ` [PATCH BlueZ v3 3/9] client/gatt: Fix setting descriptor value from scripts Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 4/9] client/mgmt: Print Connection Subrate event Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 5/9] emulator: Default to the latest BR/EDR+LE version Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 6/9] client/scripts: Add HoG device scripts Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 7/9] doc: Add functional-hog documentation Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 8/9] test: functional: add HoG tests Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 9/9] test: functional: limit the workers by the memory available Luiz Augusto von Dentz
2026-09-29 20:50 ` [PATCH BlueZ v3 0/9] Add HID over GATT functional tests 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=20260924154631.369299-3-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