From: patchwork-bot+bluetooth@kernel.org
To: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
stig@hornang.me,
syzbot+9dc8780713b11155dd74@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] Bluetooth: L2CAP: return LE credits from recvmsg under the conn lock
Date: Tue, 17 Nov 2026 18:50:10 +0000 [thread overview]
Message-ID: <179494141077.761488.1132043002777278143.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261117144938.82299-1-ngocthang2710.1999@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 17 Nov 2026 21:49:37 +0700 you wrote:
> l2cap_chan_le_send_credits() allocates an ident from conn->tx_ida, sends
> L2CAP_LE_CREDITS and frees the ident right away, since the command has
> no response. The RX path frees idents in l2cap_put_ident() under
> conn->lock. That only works if the credits path holds conn->lock too,
> so that no response can be processed between the allocation and the
> free.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: L2CAP: return LE credits from recvmsg under the conn lock
https://git.kernel.org/bluetooth/bluetooth-next/c/5beb86f98c3d
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-11-17 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 11:53 [PATCH] Bluetooth: L2CAP: don't reserve an ident for L2CAP_LE_CREDITS Nguyen Ngoc Thang
2026-11-15 18:08 ` bluez.test.bot
2026-11-16 17:04 ` [PATCH] " Luiz Augusto von Dentz
2026-11-17 14:49 ` [PATCH v2] Bluetooth: L2CAP: return LE credits from recvmsg under the conn lock Nguyen Ngoc Thang
2026-11-17 18:50 ` 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=179494141077.761488.1132043002777278143.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=ngocthang2710.1999@gmail.com \
--cc=stig@hornang.me \
--cc=syzbot+9dc8780713b11155dd74@syzkaller.appspotmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.