From: patchwork-bot+bluetooth@kernel.org
To: Siwei Zhang <oss@fourdim.xyz>
Cc: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v4 1/6] Bluetooth: L2CAP: Reject mode changes on connected channels
Date: Wed, 14 Oct 2026 17:20:08 +0000 [thread overview]
Message-ID: <179199840801.2868755.12692933554278230678.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013153720.2635387-1-oss@fourdim.xyz>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 13 Oct 2026 11:36:33 -0400 you wrote:
> A peer can send a configuration response with an RFC
> option for another mode to a connected channel, for
> example to switch it from Streaming to ERTM mode.
> l2cap_parse_conf_rsp() then changes chan->mode, but
> l2cap_ertm_init() is not called again, so the ERTM
> sequence lists are never allocated. The next
> out-of-sequence I-frame makes l2cap_seq_list_clear()
> write through the NULL srej_list.list.
>
> [...]
Here is the summary with links:
- [v4,1/6] Bluetooth: L2CAP: Reject mode changes on connected channels
https://git.kernel.org/bluetooth/bluetooth-next/c/0ac766c5ed8b
- [v4,2/6] Bluetooth: L2CAP: Reject signalling responses in invalid states
https://git.kernel.org/bluetooth/bluetooth-next/c/0ff5a6d955bd
- [v4,3/6] Bluetooth: L2CAP: Reject invalid TxWindow in configuration requests
https://git.kernel.org/bluetooth/bluetooth-next/c/2c5c3688eb61
- [v4,4/6] Bluetooth: L2CAP: Use default TxWindow for zero socket option
https://git.kernel.org/bluetooth/bluetooth-next/c/da927e6e6bf5
- [v4,5/6] Bluetooth: L2CAP: Only accept connection responses to outstanding requests
https://git.kernel.org/bluetooth/bluetooth-next/c/c3412d73414a
- [v4,6/6] Bluetooth: L2CAP: Remove dead configuration state code
https://git.kernel.org/bluetooth/bluetooth-next/c/734dbeb9338d
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-10-14 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 15:36 [PATCH v4 1/6] Bluetooth: L2CAP: Reject mode changes on connected channels Siwei Zhang
2026-10-13 15:36 ` [PATCH v4 2/6] Bluetooth: L2CAP: Reject signalling responses in invalid states Siwei Zhang
2026-10-13 15:36 ` [PATCH v4 3/6] Bluetooth: L2CAP: Reject invalid TxWindow in configuration requests Siwei Zhang
2026-10-13 15:36 ` [PATCH v4 4/6] Bluetooth: L2CAP: Use default TxWindow for zero socket option Siwei Zhang
2026-10-13 15:36 ` [PATCH v4 5/6] Bluetooth: L2CAP: Only accept connection responses to outstanding requests Siwei Zhang
2026-10-13 15:36 ` [PATCH v4 6/6] Bluetooth: L2CAP: Remove dead configuration state code Siwei Zhang
2026-10-13 20:18 ` [v4,1/6] Bluetooth: L2CAP: Reject mode changes on connected channels bluez.test.bot
2026-10-14 17:20 ` 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=179199840801.2868755.12692933554278230678.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=oss@fourdim.xyz \
/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.