From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?q?=C5=81ukasz_Rymanowski_=3Clukasz=2Erymanowski=40codecoup=2Epl=3E?=@ci.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 0/1] Btmon: Fix handling not complete packets
Date: Tue, 14 Mar 2023 19:50:19 +0000 [thread overview]
Message-ID: <167882341960.5310.13189620230834104699.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230311233640.103858-1-lukasz.rymanowski@codecoup.pl>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 12 Mar 2023 00:36:39 +0100 you wrote:
> When for security reasons or any other, packets in the btsnoop logs are
> not complete, then Included length is smaller then Original size.
>
> For the moment, Bluez always assumes to get complete packets.
> If it not happen, then it stops decoding after fist packet which
> Original size is bigger then Included lenght. e.g.
> In the file where we had some ISO packets but with payload = 0,
> btmon ended like that:
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/1] btmon: Fix decoding truncated data
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6ae44c74aaf9
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:[~2023-03-14 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 23:36 [PATCH BlueZ v2 0/1] Btmon: Fix handling not complete packets Łukasz Rymanowski
2023-03-11 23:36 ` [PATCH BlueZ v2 1/1] btmon: Fix decoding truncated data Łukasz Rymanowski
2023-03-12 2:15 ` Btmon: Fix handling not complete packets bluez.test.bot
2023-03-14 19: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=167882341960.5310.13189620230834104699.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?q?=C5=81ukasz_Rymanowski_=3Clukasz=2Erymanowski=40codecoup=2Epl=3E?=@ci.codeaurora.org \
--cc=linux-bluetooth@vger.kernel.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 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.