All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Chengfeng Ye <nicoyip.dev@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_sync: Protect UUID list traversal
Date: Mon, 20 Jul 2026 20:20:12 +0000	[thread overview]
Message-ID: <178457881239.4151939.8896306930179003502.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260719162427.2902105-1-nicoyip.dev@gmail.com>

Hello:

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

On Mon, 20 Jul 2026 00:24:27 +0800 you wrote:
> The hci_sync conversion moved class-of-device and EIR generation from an
> HCI request built under hdev->lock to asynchronous command sync work.
> The worker holds hdev->req_lock, but that lock does not serialize access
> to hdev->uuids against add_uuid() and remove_uuid(), which update the
> list under hdev->lock.
> 
> The following interleaving can therefore occur:
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_sync: Protect UUID list traversal
    https://git.kernel.org/bluetooth/bluetooth-next/c/9348bd469f56

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-19 16:24 [PATCH] Bluetooth: hci_sync: Protect UUID list traversal Chengfeng Ye
2026-07-19 17:48 ` bluez.test.bot
2026-07-20 20: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=178457881239.4151939.8896306930179003502.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=nicoyip.dev@gmail.com \
    --cc=stable@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 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.