From: Mikhail <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b7d71e: a2dp: Fix loading of remote SEP from cache
Date: Fri, 10 Jul 2026 10:24:41 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/82af2b-b7d71e@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: b7d71e5067856b0daf2f1f73b3fc95483236610e
https://github.com/bluez/bluez/commit/b7d71e5067856b0daf2f1f73b3fc95483236610e
Author: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Date: 2026-07-10 (Fri, 10 Jul 2026)
Changed paths:
M profiles/audio/a2dp.c
Log Message:
-----------
a2dp: Fix loading of remote SEP from cache
Commit 912f5efb0dd9 ("a2dp: Fix handling of codec capability storage")
added an 'i >= 2' condition to the loop that parses the stored codec
capabilities. Since i starts at 0 the loop body never runs, i stays 0,
and the subsequent 'if (i != size)' check discards every endpoint found
in the cache:
load_remote_sep() Unable to load LastUsed: rseid 6 not found
With no remote SEP loaded, avdtp_discover() can no longer take the
cached path and issues AVDTP Discover/Get All Capabilities on every
reconnect, and a2dp_setup_remote_path() returns NULL so the transport
ends up at /org/bluez/hciX/dev_YY/fd0 instead of .../sepN/fd0.
The condition was presumably meant to bound the writes into data[128],
which the original commit did not actually fix: caps is read with
'%512s' so size / 2 can be up to 256. Validate size up front instead.
Fixes: https://github.com/bluez/bluez/issues/2285
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-10 17:24 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/master/82af2b-b7d71e@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 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.