From: patchwork-bot+bluetooth@kernel.org
To: Aldo Ariel Panzardo <qwe.aldo@gmail.com>
Cc: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: ISO: balance the parent hold in hci_bind_bis()
Date: Wed, 16 Sep 2026 18:00:13 +0000 [thread overview]
Message-ID: <178958161343.2777538.8562575351949671610.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260915160332.3107274-1-qwe.aldo@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, 15 Sep 2026 13:03:32 -0300 you wrote:
> hci_conn_link() takes a lifetime reference to its parent with
> hci_conn_get(), but only takes an operational hold on the child.
> hci_conn_unlink() later balances both a hold and a reference on the
> parent.
>
> The SCO and CIS paths pass a parent acquired from a connect helper, so
> it already has a hold. For an additional BIS, hci_bind_bis() obtains the
> parent from hci_conn_hash_lookup_big(), which returns a bare pointer.
> Unlinking the child then drops the parent's existing hold and can
> schedule it for disconnection while its socket is still using it.
>
> [...]
Here is the summary with links:
- Bluetooth: ISO: balance the parent hold in hci_bind_bis()
https://git.kernel.org/bluetooth/bluetooth-next/c/4c94557dd025
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-09-16 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 16:03 [PATCH] Bluetooth: ISO: balance the parent hold in hci_bind_bis() Aldo Ariel Panzardo
2026-09-15 17:43 ` bluez.test.bot
2026-09-16 18:00 ` 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=178958161343.2777538.8562575351949671610.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=qwe.aldo@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.