From: patchwork-bot+bluetooth@kernel.org
To: Hyunwoo Kim <imv4bel@gmail.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del()
Date: Mon, 23 Mar 2026 19:40:07 +0000 [thread overview]
Message-ID: <177429480703.286640.15279296470802604075.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ab0pBlGrvw_SHFwB@v4bel>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 20 Mar 2026 20:01:26 +0900 you wrote:
> l2cap_conn_del() calls cancel_delayed_work_sync() for both info_timer
> and id_addr_timer while holding conn->lock. However, the work functions
> l2cap_info_timeout() and l2cap_conn_update_id_addr() both acquire
> conn->lock, creating a potential AB-BA deadlock if the work is already
> executing when l2cap_conn_del() takes the lock.
>
> Move the work cancellations before acquiring conn->lock and use
> disable_delayed_work_sync() to additionally prevent the works from
> being rearmed after cancellation, consistent with the pattern used in
> hci_conn_del().
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del()
https://git.kernel.org/bluetooth/bluetooth-next/c/f6bba07f059c
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-03-23 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 11:01 [PATCH v2] Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del() Hyunwoo Kim
2026-03-20 11:25 ` [v2] " bluez.test.bot
2026-03-23 19:40 ` 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=177429480703.286640.15279296470802604075.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=imv4bel@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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