Linux bluetooth development
 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, baijiaju1990@gmail.com
Subject: Re: [PATCH v3] Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update
Date: Tue, 07 Jul 2026 17:30:11 +0000	[thread overview]
Message-ID: <178344541188.2101608.13776117493322216001.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260707041518.2799385-1-zzzccc427@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,  7 Jul 2026 12:15:18 +0800 you wrote:
> MGMT_OP_LOAD_CONN_PARAM queues conn_update_sync() when a single parameter
> update changes an existing LE central connection. The queued work currently
> stores a borrowed hci_conn_params entry from hdev->le_conn_params. A later
> LOAD_CONN_PARAM request can clear disabled parameters and free that entry
> before hci_cmd_sync_work() runs the queued callback.
> 
> Do not keep the borrowed hci_conn_params pointer in queued work. Queue the
> hci_conn instead and hold a reference until the queued callback completes.
> When the work runs, revalidate that the connection is still present, look
> up the current hci_conn_params entry, and cancel the update if userspace
> removed that entry while the work was pending.
> 
> [...]

Here is the summary with links:
  - [v3] Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update
    https://git.kernel.org/bluetooth/bluetooth-next/c/3fbd73d24dcc

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  4:15 [PATCH v3] Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update Cen Zhang
2026-07-07  6:25 ` [v3] " bluez.test.bot
2026-07-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=178344541188.2101608.13776117493322216001.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=baijiaju1990@gmail.com \
    --cc=linux-bluetooth@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