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 ERTM re-init and zero pdu_len infinite loop
Date: Mon, 23 Mar 2026 19:40:05 +0000 [thread overview]
Message-ID: <177429480578.286640.8792762831934128933.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ab0uHv8K_Jri2J6K@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:23:10 +0900 you wrote:
> l2cap_config_req() processes CONFIG_REQ for channels in BT_CONNECTED
> state to support L2CAP reconfiguration (e.g. MTU changes). However,
> since both CONF_INPUT_DONE and CONF_OUTPUT_DONE are already set from
> the initial configuration, the reconfiguration path falls through to
> l2cap_ertm_init(), which re-initializes tx_q, srej_q, srej_list, and
> retrans_list without freeing the previous allocations and sets
> chan->sdu to NULL without freeing the existing skb. This leaks all
> previously allocated ERTM resources.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop
https://git.kernel.org/bluetooth/bluetooth-next/c/acf374fce194
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:23 [PATCH v2] Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop Hyunwoo Kim
2026-03-20 12:14 ` [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=177429480578.286640.8792762831934128933.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