From: Cen Zhang <zzzccc427@gmail.com>
To: marcel@holtmann.org, luiz.dentz@gmail.com
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
baijiaju1990@gmail.com, jjzuming@gmail.com, zzzccc427@gmail.com
Subject: [PATCH 0/2] Bluetooth: SMP: Serialize root channel updates
Date: Fri, 30 Oct 2026 22:43:55 +0800 [thread overview]
Message-ID: <pm-bluetooth-objects-candidate-0184-v7-c26e53b52c260063ab6a-0@gmail.com> (raw)
The SMP root channels in hdev->smp_data and hdev->smp_bredr_data are
used by HCI event processing under hdev->lock and by SMP receive
callbacks on hdev->workqueue. Power-off already removes them under
hdev->lock in hci_dev_close_sync(). Two other writers do not serialize
with these users:
1/2 The force_bredr_smp debugfs switch creates and removes the BR/EDR
root without hdev->lock. A connection confirmation can see a root
whose operations are not set yet, and a disable can race with
power-off and release the channel twice. Take hdev->lock in the
writer, and skip the deletion when power-off already emptied the
slot.
2/2 smp_register() replaces both roots when management powers on a
controller that is already up with HCI_AUTO_OFF set, while HCI
event processing and SMP receive callbacks can still be using the
old roots. Run the registration on hdev->workqueue, where it ran
before commit 2ff13894cfb8 ("Bluetooth: Perform HCI update for
power on synchronously"), and hold hdev->lock while it replaces
the roots. The caller waits for the work without holding
hdev->lock, which HCI event processing on that workqueue takes.
smp_register() still warns when it replaces the channels on that path.
This series only makes the replacement safe.
Cen Zhang (2):
Bluetooth: SMP: Serialize forced BR/EDR channel changes
Bluetooth: SMP: Serialize root channel replacement
net/bluetooth/hci_debugfs.c | 2 ++
net/bluetooth/smp.c | 38 +++++++++++++++++++++++++++++++++++--
net/bluetooth/smp.h | 3 ++-
3 files changed, 40 insertions(+), 3 deletions(-)
---
next reply other threads:[~2026-10-30 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 14:43 Cen Zhang [this message]
2026-10-30 14:43 ` [PATCH 1/2] Bluetooth: SMP: Serialize forced BR/EDR channel changes Cen Zhang
2026-10-30 14:43 ` [PATCH 2/2] Bluetooth: SMP: Serialize root channel replacement Cen Zhang
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=pm-bluetooth-objects-candidate-0184-v7-c26e53b52c260063ab6a-0@gmail.com \
--to=zzzccc427@gmail.com \
--cc=baijiaju1990@gmail.com \
--cc=jjzuming@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