From: patchwork-bot+bluetooth@kernel.org
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
marcel@holtmann.org, luiz.dentz@gmail.com, liqiang01@kylinos.cn
Subject: Re: [PATCH] Bluetooth: btmrvl: fix event packet length validation
Date: Tue, 04 Aug 2026 17:40:07 +0000 [thread overview]
Message-ID: <178586520763.3702995.8912183304786882050.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260804094632.87581-1-m.szyprowski@samsung.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 4 Aug 2026 11:46:30 +0200 you wrote:
> The event length validation added by 75e574f6a212 commit used a single
> check against sizeof(*event), which assumed every event type uses the
> maximum payload size. Unfortunately event packet length depends on the
> type of the received event, so it must be checked separately for each
> event type to avoid rejecting some known well-formed events.
>
> Fixes: 75e574f6a212 ("Bluetooth: btmrvl: validate event packet lengths")
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>
> [...]
Here is the summary with links:
- Bluetooth: btmrvl: fix event packet length validation
https://git.kernel.org/bluetooth/bluetooth-next/c/d56d51cc0cb6
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-08-04 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260804094640eucas1p1697cf118046108ce0d9d24127f68af12@eucas1p1.samsung.com>
2026-08-04 9:46 ` [PATCH] Bluetooth: btmrvl: fix event packet length validation Marek Szyprowski
2026-08-04 17: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=178586520763.3702995.8912183304786882050.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqiang01@kylinos.cn \
--cc=luiz.dentz@gmail.com \
--cc=m.szyprowski@samsung.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