From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 5051e5: lib: add iso_data_* macros to hci.h
Date: Fri, 10 Jul 2026 10:25:40 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1125495/000000-9e3c1d@github.com> (raw)
Branch: refs/heads/1125495
Home: https://github.com/bluez/bluez
Commit: 5051e5a45f44cceaef0cb1bff87fb52c126571f9
https://github.com/bluez/bluez/commit/5051e5a45f44cceaef0cb1bff87fb52c126571f9
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-07-10 (Fri, 10 Jul 2026)
Changed paths:
M lib/bluetooth/hci.h
Log Message:
-----------
lib: add iso_data_* macros to hci.h
Add macros for parsing ISO Data Packet header items.
Commit: 9e3c1d50e95b0013587f4a8fdbb71ee524beb507
https://github.com/bluez/bluez/commit/9e3c1d50e95b0013587f4a8fdbb71ee524beb507
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-07-10 (Fri, 10 Jul 2026)
Changed paths:
M monitor/packet.c
Log Message:
-----------
monitor: fix parsing of ISO packet data header and slen check
Check PB flag to see whether timestamp and data headers are present.
Check bounds before accessing data. Bump handle_str length to fit
maximum.
Byteswap length values, and mask Packet_Status_Flag correctly. Remove
SDU length check, as we are not tracking fragmentation.
Fixes: https://github.com/bluez/bluez/issues/2292
Assisted-by: GLM-5.2
Compare: https://github.com/bluez/bluez/compare/5051e5a45f44%5E...9e3c1d50e95b
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-10 17:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1125495/000000-9e3c1d@github.com \
--to=noreply@github.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox