From: mkaros <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 645bd5: audio: Fix stale AVDTP connecting state
Date: Wed, 30 Sep 2026 07:10:27 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1176758/000000-645bd5@github.com> (raw)
Branch: refs/heads/1176758
Home: https://github.com/bluez/bluez
Commit: 645bd51a50b2a5e7606268599e73d99cae72da96
https://github.com/bluez/bluez/commit/645bd51a50b2a5e7606268599e73d99cae72da96
Author: Kun Ma <mk02092022@gmail.com>
Date: 2026-09-30 (Wed, 30 Sep 2026)
Changed paths:
M profiles/audio/sink.c
M profiles/audio/source.c
Log Message:
-----------
audio: Fix stale AVDTP connecting state
When a remote dual-role A2DP device reconnects autonomously, both sink
and source services transition to their respective CONNECTING states
upon AVDTP_SESSION_STATE_CONNECTING.
If the remote device only configures one direction (e.g. initiating a
stream from remote Source to local Sink), the unused direction's state
remains stuck in CONNECTING even after the underlying AVDTP session has
reached AVDTP_SESSION_STATE_CONNECTED.
Subsequently, when policy or userspace attempts to initiate audio
playback (e.g. via sink_connect() or source_connect()), the call fails
immediately with -EBUSY due to this stale CONNECTING state.
Fix this by only returning -EBUSY if the underlying AVDTP session is
actually still in AVDTP_SESSION_STATE_CONNECTING. In addition, check if
a stream already exists on that service to prevent concurrent stream
allocations while the session is connected.
Link: https://github.com/bluez/bluez/issues/2381
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-30 14:10 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/1176758/000000-645bd5@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