From: patchwork-bot+bluetooth@kernel.org
To: syzbot <syzbot@kernel.org>
Cc: syzkaller-bugs@googlegroups.com, nogikh@google.com,
linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
marcel@holtmann.org, hildawu@realtek.com,
linux-kernel@vger.kernel.org, syzbot@lists.linux.dev
Subject: Re: [PATCH] Bluetooth: hci_core: Fix race condition during device registration
Date: Mon, 31 Aug 2026 17:20:16 +0000 [thread overview]
Message-ID: <178819681664.671757.11271710951105188207.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <7f282e86-b9fa-4a3d-8dea-208975771b35@mail.kernel.org>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 28 Aug 2026 08:55:09 +0000 (UTC) you wrote:
> From: Aleksandr Nogikh <nogikh@google.com>
>
> In hci_register_dev(), the power_on work item is queued to
> hdev->req_workqueue before initializing hdev->adv_monitors_idr and
> registering the MSFT extension via msft_register(). For devices marked with
> quirks such as HCI_QUIRK_RAW_DEVICE, the HCI_UNCONFIGURED flag is set on
> the device. When the power_on work item runs concurrently on another CPU,
> hci_power_on() detects that the device is unconfigured and immediately
> invokes hci_dev_do_close(), which calls msft_do_close().
>
> [...]
Here is the summary with links:
- Bluetooth: hci_core: Fix race condition during device registration
https://git.kernel.org/bluetooth/bluetooth-next/c/78f08df9649c
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-08-31 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 8:55 [PATCH] Bluetooth: hci_core: Fix race condition during device registration syzbot
2026-08-28 12:25 ` bluez.test.bot
2026-08-31 17:20 ` 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=178819681664.671757.11271710951105188207.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=hildawu@realtek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=nogikh@google.com \
--cc=syzbot@kernel.org \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.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