From: patchwork-bot+bluetooth@kernel.org
To: Arseniy Krasnov <avkrasnov@salutedevices.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, oxffffaa@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@salutedevices.com
Subject: Re: [RESEND PATCH v2] Bluetooth: hci_uart: fix race during initialization
Date: Mon, 03 Feb 2025 21:40:40 +0000 [thread overview]
Message-ID: <173861884028.3508836.1017363008098820182.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <3674b7a9-109e-19d7-4db8-02e9a724c314@salutedevices.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 30 Jan 2025 21:43:26 +0300 you wrote:
> 'hci_register_dev()' calls power up function, which is executed by
> kworker - 'hci_power_on()'. This function does access to bluetooth chip
> using callbacks from 'hci_ldisc.c', for example 'hci_uart_send_frame()'.
> Now 'hci_uart_send_frame()' checks 'HCI_UART_PROTO_READY' bit set, and
> if not - it fails. Problem is that 'HCI_UART_PROTO_READY' is set after
> 'hci_register_dev()', and there is tiny chance that 'hci_power_on()' will
> be executed before setting this bit. In that case HCI init logic fails.
>
> [...]
Here is the summary with links:
- [RESEND,v2] Bluetooth: hci_uart: fix race during initialization
https://git.kernel.org/bluetooth/bluetooth-next/c/c411c62cc133
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-02-03 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 8:12 [PATCH v2] Bluetooth: hci_uart: fix race during initialization Arseniy Krasnov
2024-12-17 8:37 ` [v2] " bluez.test.bot
2024-12-19 18:42 ` [PATCH v2] " Arseniy Krasnov
2024-12-19 19:01 ` Luiz Augusto von Dentz
2024-12-19 20:07 ` Arseniy Krasnov
2024-12-19 19:18 ` Luiz Augusto von Dentz
2024-12-19 20:07 ` Arseniy Krasnov
2025-01-08 12:39 ` Arseniy Krasnov
2025-01-30 18:34 ` Arseniy Krasnov
2025-01-30 18:37 ` Luiz Augusto von Dentz
2025-01-30 18:34 ` Arseniy Krasnov
2025-01-30 18:43 ` [RESEND PATCH " Arseniy Krasnov
2025-01-30 19:01 ` [RESEND,v2] " bluez.test.bot
2025-02-03 21:40 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-01 16:24 [RESEND PATCH v2] " Arseniy Krasnov
2025-02-03 21:40 ` patchwork-bot+bluetooth
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=173861884028.3508836.1017363008098820182.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=avkrasnov@salutedevices.com \
--cc=kernel@salutedevices.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=oxffffaa@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