Re: [PATCH RESEND v2 1/3] Bluetooth: L2CAP: avoid maybe-return-locked in l2cap_get_chan_by_scid/dcid
| Newsgroups | dev.linux.lists.llvm,org.kernel.vger.linux-bluetooth,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178699596338.1691257.6779779933672558121.git-patchwork-notify@kernel.org> |
Hello: This series was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz <[email protected]>: 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 <[email protected]> > Signed-off-by: Pauli Virtanen <[email protected]> > > [...] 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