From: patchwork-bot+bluetooth@kernel.org
To: Iulia Tanasescu <iulia.tanasescu@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, claudia.rosu@nxp.com,
mihai-octavian.urzica@nxp.com, silviu.barbulescu@nxp.com,
vlad.pruteanu@nxp.com, andrei.istodorescu@nxp.com,
luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ 0/1] btdev: Fix set PA data array overflow
Date: Tue, 13 Feb 2024 20:50:29 +0000 [thread overview]
Message-ID: <170785742904.22526.6089462734795932052.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240213155803.3159-1-iulia.tanasescu@nxp.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 13 Feb 2024 17:58:02 +0200 you wrote:
> This fixes an array overflow that can happen if the user issues the
> LE Set Periodic Advertising Data command with data length exceeding
> 31 bytes.
>
> This can be noticed when running the Broadcast Source/Sink scenarios
> in bluetoothctl, using emulated controllers: If the source BASE
> exceeds 31 bytes, the PA reports received by the Sink looks something
> like the following:
>
> [...]
Here is the summary with links:
- [BlueZ,1/1] btdev: Fix set PA data array overflow
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7c49568a2758
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:[~2024-02-13 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 15:58 [PATCH BlueZ 0/1] btdev: Fix set PA data array overflow Iulia Tanasescu
2024-02-13 15:58 ` [PATCH BlueZ 1/1] " Iulia Tanasescu
2024-02-13 17:10 ` bluez.test.bot
2024-02-13 20: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=170785742904.22526.6089462734795932052.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=andrei.istodorescu@nxp.com \
--cc=claudia.rosu@nxp.com \
--cc=iulia.tanasescu@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=mihai-octavian.urzica@nxp.com \
--cc=silviu.barbulescu@nxp.com \
--cc=vlad.pruteanu@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).