From: patchwork-bot+bluetooth@kernel.org
To: Cen Zhang <zzzccc427@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
baijiaju1990@gmail.com, jjzuming@gmail.com
Subject: Re: [PATCH 0/4] Bluetooth: Keep borrowed keys inside RCU sections
Date: Fri, 30 Oct 2026 14:00:07 +0000 [thread overview]
Message-ID: <179336880729.1091505.16673199626130104099.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0122-v8-952ad9eb0ef59367ba6a-0@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 29 Oct 2026 21:12:25 +0800 you wrote:
> hci_find_link_key(), hci_find_ltk() and hci_find_irk_by_addr() return
> entries of RCU-protected lists after leaving their read-side sections.
> Management clears and reloads these lists under hdev->lock, and
> kfree_rcu() frees the old entries after a grace period. A user that
> does not hold hdev->lock must therefore keep the returned entry inside
> its own RCU read-side section until it has finished reading it.
>
> [...]
Here is the summary with links:
- [1/4] Bluetooth: hci_core: Keep link-key filtering inside RCU
https://git.kernel.org/bluetooth/bluetooth-next/c/b5bcffa76cbe
- [2/4] Bluetooth: SMP: Protect link keys during LTK derivation
https://git.kernel.org/bluetooth/bluetooth-next/c/a7a9d27def4b
- [3/4] Bluetooth: SMP: Protect LTK encryption with RCU
https://git.kernel.org/bluetooth/bluetooth-next/c/5b9045b0a114
- [4/4] Bluetooth: hci_sync: Copy the resolving-list IRK under RCU
https://git.kernel.org/bluetooth/bluetooth-next/c/c278da2c4761
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-10-30 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 13:12 [PATCH 0/4] Bluetooth: Keep borrowed keys inside RCU sections Cen Zhang
2026-10-29 13:12 ` [PATCH 1/4] Bluetooth: hci_core: Keep link-key filtering inside RCU Cen Zhang
2026-10-29 14:50 ` Bluetooth: Keep borrowed keys inside RCU sections bluez.test.bot
2026-10-29 13:12 ` [PATCH 2/4] Bluetooth: SMP: Protect link keys during LTK derivation Cen Zhang
2026-10-29 13:12 ` [PATCH 3/4] Bluetooth: SMP: Protect LTK encryption with RCU Cen Zhang
2026-10-29 13:12 ` [PATCH 4/4] Bluetooth: hci_sync: Copy the resolving-list IRK under RCU Cen Zhang
2026-10-30 14: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=179336880729.1091505.16673199626130104099.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=baijiaju1990@gmail.com \
--cc=jjzuming@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=zzzccc427@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