From: patchwork-bot+bluetooth@kernel.org
To: Cen Zhang <zzzccc427@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
baijiaju1990@gmail.com, jjzuming@gmail.com
Subject: Re: [PATCH] Bluetooth: MGMT: Reject quality report requests during unregister
Date: Wed, 07 Oct 2026 17:30:07 +0000 [thread overview]
Message-ID: <179139420777.3628206.6252425087306372679.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0186-v1-e03b4f1d5ba49b962cec@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 6 Oct 2026 15:24:31 +0800 you wrote:
> A quality report request must not call a driver callback after its
> module text has been released. hci_mgmt_cmd() holds an hci_dev reference
> through set_exp_feature(), but that reference only preserves the device
> allocation. set_quality_report_func() takes req_lock and invokes
> hdev->set_quality_report without checking HCI_UNREGISTER.
>
> This is unsafe when a SET_EXP_FEATURE request for an Intel controller
> would change HCI_QUALITY_REPORT and is delayed before taking req_lock
> while the controller is removed. With btintel_pcie and btintel built as
> modules and no other btintel dependents, the following order is
> possible:
>
> [...]
Here is the summary with links:
- Bluetooth: MGMT: Reject quality report requests during unregister
https://git.kernel.org/bluetooth/bluetooth-next/c/ba9fb67965c9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-07 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 7:24 Cen Zhang
2026-10-07 17:30 ` patchwork-bot+bluetooth [this message]
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=179139420777.3628206.6252425087306372679.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--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 \
--cc=zzzccc427@gmail.com \
/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®