From: "Andrei A. Bykov" <andreiab9019@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] Bluetooth: hci_event: keep event waiters pending on unrelated replies
Date: Sat, 21 Nov 2026 00:31:03 -0300 [thread overview]
Message-ID: <20261121033104.441146-2-andreiab9019@gmail.com> (raw)
In-Reply-To: <20261121033104.441146-1-andreiab9019@gmail.com>
An incoming bonded LE connection may issue LE Read Remote Features and
wait for its terminal event while responding to an LTK Request with an
asynchronous LTK Request Reply.
hci_req_cmd_complete() accepts the reply as a valid sent command but
selects the completion callback from req_skb. If req_skb still belongs to
Remote Features, the LTK reply completes that request before its terminal
event arrives. This releases the feature hold while the connection is
still in BT_CONFIG and can immediately disconnect it.
Keep an active request with a terminal event pending when a valid reply
belongs to a different opcode. Apply the guard to Command Complete and
Command Status after command-specific handling and command-credit
updates, and continue scheduling queued commands.
Limit the guard to an active waiter. Replies following cancellation or
timeout retain the existing pending-flag cleanup. Unmatched replies still
reach the spontaneous Reset recovery path, and matching replies retain
their existing completion semantics.
Observed with an Intel AX210 peripheral, BlueZ 5.88 and a bonded Windows
central. Three unpatched attempts disconnected immediately after LTK
Reply completion, before Remote Features completion.
Fixes: 2615fd9a7c25 ("Bluetooth: hci_sync: Fix overwriting request callback")
Signed-off-by: Andrei A. Bykov <andreiab9019@gmail.com>
---
net/bluetooth/hci_event.c | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
index ab875b9..5281551 100644
--- a/net/bluetooth/hci_event.c
+++ b/net/bluetooth/hci_event.c
@@ -4862,6 +4862,18 @@ static void hci_cmd_complete_evt(struct hci_dev *hdev, void *data,
handle_cmd_cnt_and_timer(hdev, ev->ncmd);
+ /* An unrelated command may complete while a request waits for its
+ * terminal event. Process the reply and command credits, but do not
+ * complete the pending request with that command's response.
+ * Unmatched replies must still reach hci_req_cmd_complete(), e.g.
+ * for the spontaneous Reset workaround during initialization.
+ */
+ if (READ_ONCE(hdev->req_status) == HCI_REQ_PEND &&
+ hdev->req_skb && hci_skb_event(hdev->req_skb) &&
+ hci_skb_opcode(hdev->req_skb) != *opcode &&
+ hci_sent_cmd_data(hdev, *opcode))
+ goto queue_next;
+
hci_req_cmd_complete(hdev, *opcode, *status, req_complete,
req_complete_skb);
@@ -4871,6 +4883,7 @@ static void hci_cmd_complete_evt(struct hci_dev *hdev, void *data,
return;
}
+queue_next:
if (atomic_read(&hdev->cmd_cnt) && !skb_queue_empty(&hdev->cmd_q))
queue_work(hdev->workqueue, &hdev->cmd_work);
}
@@ -4982,6 +4995,18 @@ static void hci_cmd_status_evt(struct hci_dev *hdev, void *data,
handle_cmd_cnt_and_timer(hdev, ev->ncmd);
+ /* An unrelated command may complete while a request waits for its
+ * terminal event. Process the reply and command credits, but do not
+ * complete the pending request with that command's response.
+ * Unmatched replies must still reach hci_req_cmd_complete(), e.g.
+ * for the spontaneous Reset workaround during initialization.
+ */
+ if (READ_ONCE(hdev->req_status) == HCI_REQ_PEND &&
+ hdev->req_skb && hci_skb_event(hdev->req_skb) &&
+ hci_skb_opcode(hdev->req_skb) != *opcode &&
+ hci_sent_cmd_data(hdev, *opcode))
+ goto queue_next;
+
/* Indicate request completion if the command failed. Also, if
* we're not waiting for a special event and we get a success
* command status we should try to flag the request as completed
@@ -4998,6 +5023,7 @@ static void hci_cmd_status_evt(struct hci_dev *hdev, void *data,
}
}
+queue_next:
if (atomic_read(&hdev->cmd_cnt) && !skb_queue_empty(&hdev->cmd_q))
queue_work(hdev->workqueue, &hdev->cmd_work);
}
next prev parent reply other threads:[~2026-11-21 3:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-21 3:31 [PATCH 0/2] Bluetooth: fix bonded LE peripheral reconnect completion and holds Andrei A. Bykov
2026-11-21 3:31 ` Andrei A. Bykov [this message]
2026-11-21 3:31 ` [PATCH 2/2] Bluetooth: hci_core: keep the LE feature hold until completion Andrei A. Bykov
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=20261121033104.441146-2-andreiab9019@gmail.com \
--to=andreiab9019@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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
all inboxes | Powered by JetHome®