All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Binbin Deng <18983559317@163.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	johan.hedberg@intel.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH bluetooth v1] Bluetooth: hci_core: Initialize LTK before publication
Date: Tue, 20 Oct 2026 18:20:09 +0000	[thread overview]
Message-ID: <179252040952.143064.9151877128900606863.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261019105624.489859-1-18983559317@163.com>

Hello:

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

On Mon, 19 Oct 2026 18:56:24 +0800 you wrote:
> hci_add_ltk() publishes a newly allocated LTK on hdev->long_term_keys
> before initializing its address, type, value, authentication state,
> encryption size, EDIV, and random value.  hci_find_ltk() and the debugfs
> long_term_keys_show() traverse this list under RCU and can therefore see
> a zero or partially initialized key before those stores complete.
> 
> The race is reachable by racing an LTK addition with another CPU looking
> up or dumping long-term keys.  For example, userspace can issue
> MGMT_OP_LOAD_LONG_TERM_KEYS while another process reads the corresponding
> debugfs file.
> 
> [...]

Here is the summary with links:
  - [v1] Bluetooth: hci_core: Initialize LTK before publication
    https://git.kernel.org/bluetooth/bluetooth-next/c/fd0191d9375d

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-20 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 10:56 [PATCH bluetooth v1] Bluetooth: hci_core: Initialize LTK before publication Binbin Deng
2026-10-19 14:42 ` [v1] " bluez.test.bot
2026-10-20 18:20 ` 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=179252040952.143064.9151877128900606863.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=18983559317@163.com \
    --cc=johan.hedberg@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@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 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.