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 v1] Bluetooth: hci_uart: fix race during initialization
Date: Tue, 18 Feb 2025 15:40:33 +0000 [thread overview]
Message-ID: <173989323376.4126041.7605697940734991168.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <c7f1e8e5-e752-9ea7-ffe7-0ecc282bd92a@salutedevices.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 12 Feb 2025 18:59:46 +0300 you wrote:
> Do not set 'HCI_UART_PROTO_READY' before call 'hci_uart_register_dev()'.
> Possible race is when someone calls 'hci_tty_uart_close()' after this bit
> is set, but 'hci_uart_register_dev()' wasn't done. This leads to access
> to uninitialized fields. To fix it let's set this bit after device was
> registered (as before patch c411c62cc133) and to fix previous problem let's
> add one more bit in addition to 'HCI_UART_PROTO_READY' which allows to
> perform power up without original bit set (pls see commit c411c62cc133).
>
> [...]
Here is the summary with links:
- [RESEND,v1] Bluetooth: hci_uart: fix race during initialization
https://git.kernel.org/bluetooth/bluetooth-next/c/e2040fe3b82b
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:[~2025-02-18 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 15:59 [RESEND PATCH v1] Bluetooth: hci_uart: fix race during initialization Arseniy Krasnov
2025-02-12 16:35 ` [RESEND,v1] " bluez.test.bot
2025-02-18 15:40 ` 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=173989323376.4126041.7605697940734991168.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.