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, devnexen@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: ISO: fix malformed ISO_END/CONT handling
Date: Thu, 02 Jul 2026 16:10:12 +0000 [thread overview]
Message-ID: <178300861213.1757978.17509435332853877219.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <da68c9b8242e9fbf482b1512e9d612768f2cc7e8.1782920668.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 Wed, 1 Jul 2026 18:46:38 +0300 you wrote:
> Core specification (Part C vol 4 sec 5.4.5) does not exclude empty
> ISO_CONT, ISO_END packets. We currently reject them if they are last.
>
> If controller sends malformed sequence
>
> ISO_START -> rx_len = 4, ISO_CONT skb->len 4, ISO_START
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: ISO: fix malformed ISO_END/CONT handling
https://git.kernel.org/bluetooth/bluetooth-next/c/103ac7b87e1f
- [2/2] Bluetooth: ISO: exclude RFU bits from ISO_SDU_Length
https://git.kernel.org/bluetooth/bluetooth-next/c/9496dfbab73f
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-07-02 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 15:46 [PATCH 1/2] Bluetooth: ISO: fix malformed ISO_END/CONT handling Pauli Virtanen
2026-07-01 15:46 ` [PATCH 2/2] Bluetooth: ISO: exclude RFU bits from ISO_SDU_Length Pauli Virtanen
2026-07-01 17:00 ` [1/2] Bluetooth: ISO: fix malformed ISO_END/CONT handling bluez.test.bot
2026-07-02 16:10 ` 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=178300861213.1757978.17509435332853877219.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=devnexen@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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