From: Elman Shahbazov <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 4c789b: avrcp: Split off name parsing from parse_*_element()
Date: Tue, 04 Aug 2026 06:19:47 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1140113/000000-e454c9@github.com> (raw)
Branch: refs/heads/1140113
Home: https://github.com/bluez/bluez
Commit: 4c789b22745a0b7dce8084932fd6475977927271
https://github.com/bluez/bluez/commit/4c789b22745a0b7dce8084932fd6475977927271
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-08-04 (Tue, 04 Aug 2026)
Changed paths:
M Makefile.plugins
A profiles/audio/avrcp-parse.c
A profiles/audio/avrcp-parse.h
M profiles/audio/avrcp.c
Log Message:
-----------
avrcp: Split off name parsing from parse_*_element()
This will allow us to use the name extraction code in
parse_media_element() and parse_folder_element() separately, such
as in tests.
Commit: 4093bc867ab2b2cecc857cae236ec7445b6d6432
https://github.com/bluez/bluez/commit/4093bc867ab2b2cecc857cae236ec7445b6d6432
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-08-04 (Tue, 04 Aug 2026)
Changed paths:
M Makefile.am
A unit/test-avrcp-sec.c
Log Message:
-----------
unit: Adapt poc_*_oob.c test into a new test
Adapt poc_avrcp_oob.c and poc_folder_oob.c into unit tests.
Co-authored-by: Elman Shahbazov <shahbazovelman97@gmail.com>
Commit: e454c9ca6555e997184090988fa1a2e2dcba27b6
https://github.com/bluez/bluez/commit/e454c9ca6555e997184090988fa1a2e2dcba27b6
Author: Elman Shahbazov <shahbazovelman97@gmail.com>
Date: 2026-08-04 (Tue, 04 Aug 2026)
Changed paths:
M profiles/audio/avrcp-parse.c
Log Message:
-----------
avrcp: Fix Out-of-Bounds Read in AVRCP GetFolderItems parsing
Co-Authored-by: Bastien Nocera <hadess@hadess.net>
Compare: https://github.com/bluez/bluez/compare/4c789b22745a%5E...e454c9ca6555
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-08-04 13:19 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/1140113/000000-e454c9@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;
as well as URLs for NNTP newsgroup(s).