From: patchwork-bot+bluetooth@kernel.org
To: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] vhci: Check whether vhci open setup succeeded
Date: Wed, 20 Sep 2023 21:00:24 +0000 [thread overview]
Message-ID: <169524362459.6493.8374365124272867725.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230920184313.973822-1-arkadiusz.bokowy@gmail.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 20 Sep 2023 20:43:13 +0200 you wrote:
> Due to race condition in the vhci kernel driver, we might read not a
> vendor response packet, but a HCI reset command. This extra check will
> ensure that kernel driver behaves correctly. Otherwise, the HCI setup
> process will fail, because our controller will not respond to "missing"
> HCI reset command. In result the virtual HCI will be DOWN and without
> initialized Bluetooth address, e.g:
>
> [...]
Here is the summary with links:
- [BlueZ] vhci: Check whether vhci open setup succeeded
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a2d47ef05226
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:[~2023-09-20 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 15:30 [PATCH] Bluetooth: vhci: Fix race when opening vhci device Arkadiusz Bokowy
2023-09-20 15:30 ` [PATCH BlueZ] vhci: Check whether vhci open setup succeeded Arkadiusz Bokowy
2023-09-20 16:34 ` [BlueZ] " bluez.test.bot
2023-09-20 16:04 ` Bluetooth: vhci: Fix race when opening vhci device bluez.test.bot
2023-09-20 18:43 ` [PATCH BlueZ] vhci: Check whether vhci open setup succeeded Arkadiusz Bokowy
2023-09-20 20:13 ` [BlueZ] " bluez.test.bot
2023-09-20 21:00 ` 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=169524362459.6493.8374365124272867725.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=arkadiusz.bokowy@gmail.com \
--cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).