From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, elver@google.com, bvanassche@acm.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH RESEND v2 1/3] Bluetooth: L2CAP: avoid maybe-return-locked in l2cap_get_chan_by_scid/dcid
Date: Mon, 17 Aug 2026 19:46:03 +0000 [thread overview]
Message-ID: <178699596338.1691257.6779779933672558121.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <35f8d2856ef35e1c6314101ee60b16af39d88e78.1786871620.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 16 Aug 2026 12:47:03 +0300 you wrote:
> Replace the maybe-return-locked pattern in l2cap_get_chan_by_scid/dcid()
> by doing locking in the caller after NULL check. This allows adding
> context analysis annotations for the locking.
>
> Reviewed-by: Bart Van Assche <bvanassche@acm.org>
> Signed-off-by: Pauli Virtanen <pav@iki.fi>
>
> [...]
Here is the summary with links:
- [RESEND,v2,1/3] Bluetooth: L2CAP: avoid maybe-return-locked in l2cap_get_chan_by_scid/dcid
https://git.kernel.org/bluetooth/bluetooth-next/c/a7b612da9059
- [RESEND,v2,2/3] Bluetooth: L2CAP: add locking annotations for l2cap_chan_lock/unlock
https://git.kernel.org/bluetooth/bluetooth-next/c/a3dd57c49564
- [RESEND,v2,3/3] Bluetooth: enable context analysis for headers
https://git.kernel.org/bluetooth/bluetooth-next/c/c519ffc1e2c6
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-08-17 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 9:47 [PATCH RESEND v2 1/3] Bluetooth: L2CAP: avoid maybe-return-locked in l2cap_get_chan_by_scid/dcid Pauli Virtanen
2026-08-16 9:47 ` [PATCH RESEND v2 2/3] Bluetooth: L2CAP: add locking annotations for l2cap_chan_lock/unlock Pauli Virtanen
2026-08-16 9:47 ` [PATCH RESEND v2 3/3] Bluetooth: enable context analysis for headers Pauli Virtanen
2026-08-16 10:28 ` [RESEND,v2,1/3] Bluetooth: L2CAP: avoid maybe-return-locked in l2cap_get_chan_by_scid/dcid bluez.test.bot
2026-08-17 19:46 ` 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=178699596338.1691257.6779779933672558121.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=bvanassche@acm.org \
--cc=elver@google.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pav@iki.fi \
/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