From: patchwork-bot+bluetooth@kernel.org
To: Jonathan Rissanen <jonathan.rissanen@axis.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@axis.com
Subject: Re: [PATCH v3 0/2] Bluetooth: fix race during h4 bluetooth initialization
Date: Fri, 27 Mar 2026 19:20:05 +0000 [thread overview]
Message-ID: <177463920504.3624781.2332475292539034639.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260327-hci-init-fix-v3-0-1b54bad4ef0f@axis.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 27 Mar 2026 11:47:19 +0100 you wrote:
> Hi,
>
> This series fixes a race condition that causes hci events to sometimes
> be ignored during h4 initialization.
>
> The first patch clears the HCI_UART_PROTO_INIT bit if device
> registration fails. This is needed to prevent the second patch from
> introducing a possible null pointer dereference.
>
> [...]
Here is the summary with links:
- [v3,1/2] Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error
https://git.kernel.org/bluetooth/bluetooth-next/c/c6a106ff1913
- [v3,2/2] Bluetooth: hci_h4: Fix race during initialization
https://git.kernel.org/bluetooth/bluetooth-next/c/42ee54fcd11e
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-03-27 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 10:47 [PATCH v3 0/2] Bluetooth: fix race during h4 bluetooth initialization Jonathan Rissanen
2026-03-27 10:47 ` [PATCH v3 1/2] Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error Jonathan Rissanen
2026-03-27 11:32 ` Bluetooth: fix race during h4 bluetooth initialization bluez.test.bot
2026-03-27 10:47 ` [PATCH v3 2/2] Bluetooth: hci_h4: Fix race during initialization Jonathan Rissanen
2026-03-27 19: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=177463920504.3624781.2332475292539034639.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=jonathan.rissanen@axis.com \
--cc=kernel@axis.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