From: patchwork-bot+bluetooth@kernel.org
To: Siwei Zhang <oss@fourdim.xyz>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
safa.karakus@secunnix.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen()
Date: Thu, 21 May 2026 15:30:22 +0000 [thread overview]
Message-ID: <177937742263.384060.14413660411972346162.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260521021249.3258069-1-oss@fourdim.xyz>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 20 May 2026 22:12:20 -0400 you wrote:
> l2cap_chan_close() removes the channel from conn->chan_l, which
> must be done under conn->lock. cleanup_listen() runs under the
> parent sk_lock, so acquiring conn->lock would invert the
> established conn->lock -> chan->lock -> sk_lock order.
>
> Instead of calling l2cap_chan_close() directly, schedule
> l2cap_chan_timeout with delay 0 to close the channel
> asynchronously. The timeout handler already acquires conn->lock
> and chan->lock in the correct order.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen()
https://git.kernel.org/bluetooth/bluetooth-next/c/75780ca4c6a8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-05-21 15:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 23:30 [PATCH] Bluetooth: l2cap: fix UAF race in l2cap_sock_cleanup_listen Safa Karakuş
2026-04-29 0:37 ` bluez.test.bot
2026-04-30 17:17 ` [PATCH] " Luiz Augusto von Dentz
2026-05-16 9:21 ` [PATCH v3] Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() Safa Karakuş
2026-05-16 10:18 ` [v3] " bluez.test.bot
2026-05-16 18:15 ` [PATCH v4] " Safa Karakuş
2026-05-16 20:47 ` [v4] " bluez.test.bot
2026-05-16 22:40 ` [PATCH v4] " Hillf Danton
2026-05-20 19:14 ` fourdim
2026-05-20 20:00 ` patchwork-bot+bluetooth
2026-05-20 20:05 ` [PATCH] Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen() Siwei Zhang
2026-05-20 20:29 ` Luiz Augusto von Dentz
2026-05-21 1:56 ` Siwei Zhang
2026-05-21 2:12 ` [PATCH v2] " Siwei Zhang
2026-05-21 3:57 ` [v2] " bluez.test.bot
2026-05-21 4:24 ` Siwei Zhang
2026-05-21 14:26 ` bluez.test.bot
2026-05-21 15:30 ` patchwork-bot+bluetooth [this message]
2026-05-20 21:28 ` bluez.test.bot
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=177937742263.384060.14413660411972346162.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=oss@fourdim.xyz \
--cc=safa.karakus@secunnix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox