From: patchwork-bot+bluetooth@kernel.org
To: Niels Dossche <dossche.niels@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
johan.hedberg@gmail.com, luiz.dentz@gmail.com,
ankit.p.navik@intel.com
Subject: Re: [PATCH] Bluetooth: protect le accept and resolv lists with hdev->lock
Date: Mon, 25 Apr 2022 14:30:27 +0000 [thread overview]
Message-ID: <165089702716.25646.7761597175138105526.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220422223116.70026-1-dossche.niels@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Marcel Holtmann <marcel@holtmann.org>:
On Sat, 23 Apr 2022 00:31:17 +0200 you wrote:
> Concurrent operations from events on le_{accept,resolv}_list are
> currently unprotected by hdev->lock.
> Most existing code do already protect the lists with that lock.
> This can be observed in hci_debugfs and hci_sync.
> Add the protection for these events too.
>
> Fixes: b950aa88638c ("Bluetooth: Add definitions and track LE resolve list modification")
> Fixes: 0f36b589e4ee ("Bluetooth: Track LE white list modification via HCI commands")
> Signed-off-by: Niels Dossche <dossche.niels@gmail.com>
>
> [...]
Here is the summary with links:
- Bluetooth: protect le accept and resolv lists with hdev->lock
https://git.kernel.org/bluetooth/bluetooth-next/c/df50527dbc32
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:[~2022-04-25 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 22:31 [PATCH] Bluetooth: protect le accept and resolv lists with hdev->lock Niels Dossche
2022-04-23 0:04 ` bluez.test.bot
2022-04-25 14:30 ` 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=165089702716.25646.7761597175138105526.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=ankit.p.navik@intel.com \
--cc=dossche.niels@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@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