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: Fix command skb lifetime during scan setup
Date: Tue, 06 Oct 2026 14:30:18 +0000 [thread overview]
Message-ID: <179129701852.2655967.14077509856109864264.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261004162612.3968831-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, 5 Oct 2026 00:26:12 +0800 you wrote:
> During PA sync scan setup, hci_le_set_ext_scan_param_sync() gets the
> address used for the PA_LINK lookup from hci_sent_cmd_data(). The
> returned pointer borrows storage from sent_cmd or req_skb, without
> holding a reference to either skb.
>
> The scan worker runs on req_workqueue while hci_cmd_work() runs on the
> separate device workqueue. After the scan worker loads sent_cmd, the
> command worker can free and replace it before hci_sent_cmd_data()
> dereferences the skb. The command payload can also be freed between
> returning from the helper and comparing the address. The connection
> lookup's RCU critical section does not protect the command skb.
>
> [...]
Here is the summary with links:
- Bluetooth: hci_sync: Fix command skb lifetime during scan setup
https://git.kernel.org/bluetooth/bluetooth-next/c/9af12272061d
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-06 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 16:26 [PATCH] Bluetooth: hci_sync: Fix command skb lifetime during scan setup Chengfeng Ye
2026-10-04 18:49 ` bluez.test.bot
2026-10-06 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=179129701852.2655967.14077509856109864264.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.