From: patchwork-bot+bluetooth@kernel.org
To: Runyu Xiao <runyu.xiao@seu.edu.cn>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, jtt@codenomicon.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
jianhao.xu@seu.edu.cn, stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: L2CAP: cancel pending_rx_work before taking conn->lock
Date: Mon, 22 Jun 2026 17:00:27 +0000 [thread overview]
Message-ID: <178214762700.1322955.1313476336537592947.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260617153613.1139031-1-runyu.xiao@seu.edu.cn>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 17 Jun 2026 23:36:13 +0800 you wrote:
> l2cap_conn_del() takes conn->lock and then calls cancel_work_sync() for
> pending_rx_work. process_pending_rx() takes the same mutex, so teardown
> can deadlock against the worker it is flushing.
>
> This issue was found by our static analysis tool and then manually
> reviewed against the current tree.
>
> [...]
Here is the summary with links:
- Bluetooth: L2CAP: cancel pending_rx_work before taking conn->lock
https://git.kernel.org/bluetooth/bluetooth-next/c/cfa697b22dad
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-06-22 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 15:36 [PATCH] Bluetooth: L2CAP: cancel pending_rx_work before taking conn->lock Runyu Xiao
2026-06-17 18:04 ` bluez.test.bot
2026-06-22 17: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=178214762700.1322955.1313476336537592947.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=jianhao.xu@seu.edu.cn \
--cc=johan.hedberg@gmail.com \
--cc=jtt@codenomicon.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=runyu.xiao@seu.edu.cn \
--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