From: Simon Mikuda <simon.mikuda@streamunlimited.com>
To: linux-bluetooth@vger.kernel.org
Cc: Simon Mikuda <simon.mikuda@streamunlimited.com>
Subject: [PATCH BlueZ] shared/att: Confirm indications without a registered handler
Date: Sun, 22 Nov 2026 11:35:11 +0100 [thread overview]
Message-ID: <20261122103511.647388-1-simon.mikuda@streamunlimited.com> (raw)
When no GATT client is attached to the bearer nothing registers for
Handle Value Indication, so handle_notify() answers it with an Error
Response. That is not a valid reply to an indication (Core Vol 3,
Part F, 3.4.7.2 allows only a Handle Value Confirmation): the peer
keeps waiting for the confirmation and drops the link when its 30
second ATT transaction timeout expires.
This happens on incoming connections when ReverseServiceDiscovery or
[GATT] Client is disabled in main.conf. iOS sends Service Changed as
the first PDU on every bonded reconnect:
> ACL Data RX: Handle 64 flags 0x02 dlen 11
ATT: Handle Value Indication (0x1d) len 6
Handle: 0x0008
Data: 0a00ffff
< ACL Data TX: Handle 64 flags 0x00 dlen 9
ATT: Error Response (0x01) len 4
Handle Value Indication (0x1d)
Handle: 0x0000
Error: Request Not Supported (0x06)
...
> HCI Event: Disconnect Complete (0x05) plen 4 #113 34.912832
Status: Success (0x00)
Handle: 64
Reason: Remote User Terminated Connection (0x13)
Send the confirmation on the bearer the indication arrived on when no
handler is registered. With a GATT client attached it confirms as
before.
Assisted-by: Claude:claude-opus-5-5
---
src/shared/att.c | 19 +++++++++++++------
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/src/shared/att.c b/src/shared/att.c
index 366ee83d8..bf869cc81 100644
--- a/src/shared/att.c
+++ b/src/shared/att.c
@@ -1086,12 +1086,19 @@ static void handle_notify(struct bt_att_chan *chan, uint8_t *pdu,
}
not_supported:
- /*
- * If this was not a command and no handler was registered for it,
- * respond with "Not Supported"
- */
- if (!found && get_op_type(opcode) != ATT_OP_TYPE_CMD)
- respond_not_supported(att, opcode);
+ if (!found) {
+ /*
+ * An indication can only be answered with a confirmation, an
+ * Error Response leaves the peer waiting until its ATT
+ * transaction times out. If this was not a command and no
+ * handler was registered for it, respond with "Not Supported".
+ */
+ if (opcode == BT_ATT_OP_HANDLE_IND)
+ bt_att_chan_send(chan, BT_ATT_OP_HANDLE_CONF, NULL, 0,
+ NULL, NULL, NULL);
+ else if (get_op_type(opcode) != ATT_OP_TYPE_CMD)
+ respond_not_supported(att, opcode);
+ }
bt_att_unref(att);
}
base-commit: 1adfe662efeff12997df9ddd0960dbd0de9c8ea7
--
2.43.0
next reply other threads:[~2026-11-22 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 10:35 Simon Mikuda [this message]
2026-11-22 18:30 ` [BlueZ] shared/att: Confirm indications without a registered handler bluez.test.bot
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=20261122103511.647388-1-simon.mikuda@streamunlimited.com \
--to=simon.mikuda@streamunlimited.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;
as well as URLs for NNTP newsgroup(s).