All of lore.kernel.org
 help / color / mirror / Atom feed
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] Bluetooth: hci_core: Keep RCU protection through LTK filtering
Date: Wed, 07 Oct 2026 17:30:10 +0000	[thread overview]
Message-ID: <179139421077.3628206.11889027224704009743.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0123-v5-83023fa5b4741c350341@gmail.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue,  6 Oct 2026 15:38:38 +0800 you wrote:
> The LTK selected by hci_find_ltk() must remain allocated while its
> value is checked against the blocked-key list. The finder releases RCU
> before passing k->val to hci_is_blocked_key(). The helper's own RCU
> section protects the blocked-key list, but the selected LTK may already
> have been reclaimed before that section starts.
> 
> An LE ATT socket security request can reach smp_ltk_encrypt() without
> holding hdev->lock. With a matching stored LTK and an LTK-type
> blocked-key entry present, a concurrent MGMT_OP_LOAD_LONG_TERM_KEYS can
> remove the selected LTK in the following order:
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_core: Keep RCU protection through LTK filtering
    https://git.kernel.org/bluetooth/bluetooth-next/c/6a46ef87a65c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-07 17:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06  7:38 [PATCH] Bluetooth: hci_core: Keep RCU protection through LTK filtering Cen Zhang
2026-10-06  8:34 ` bluez.test.bot
2026-10-07 17: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=179139421077.3628206.11889027224704009743.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 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.