From: Kun Ma <mk02092022@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Kun Ma <mk02092022@gmail.com>
Subject: [PATCH BlueZ] audio: Fix stale AVDTP connecting state
Date: Wed, 30 Sep 2026 18:12:40 +0800 [thread overview]
Message-ID: <20260930101242.43592-1-mk02092022@gmail.com> (raw)
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
---
profiles/audio/sink.c | 6 +++++-
profiles/audio/source.c | 6 +++++-
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/profiles/audio/sink.c b/profiles/audio/sink.c
index 81d5a3a6b..3363f421f 100644
--- a/profiles/audio/sink.c
+++ b/profiles/audio/sink.c
@@ -281,7 +281,11 @@ int sink_connect(struct btd_service *service)
if (sink->connect_id > 0 || sink->disconnect_id > 0)
return -EBUSY;
- if (sink->state == SINK_STATE_CONNECTING)
+ if (sink->state == SINK_STATE_CONNECTING &&
+ sink->session_state == AVDTP_SESSION_STATE_CONNECTING)
+ return -EBUSY;
+
+ if (sink->stream)
return -EBUSY;
if (sink->stream_state >= AVDTP_STATE_OPEN)
diff --git a/profiles/audio/source.c b/profiles/audio/source.c
index 6be4de74e..54f9c4a4e 100644
--- a/profiles/audio/source.c
+++ b/profiles/audio/source.c
@@ -282,7 +282,11 @@ int source_connect(struct btd_service *service)
if (source->connect_id > 0 || source->disconnect_id > 0)
return -EBUSY;
- if (source->state == SOURCE_STATE_CONNECTING)
+ if (source->state == SOURCE_STATE_CONNECTING &&
+ source->session_state == AVDTP_SESSION_STATE_CONNECTING)
+ return -EBUSY;
+
+ if (source->stream)
return -EBUSY;
if (source->stream_state >= AVDTP_STATE_OPEN)
--
2.55.0
next reply other threads:[~2026-09-30 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 10:12 Kun Ma [this message]
2026-09-30 15:15 ` [BlueZ] audio: Fix stale AVDTP connecting state bluez.test.bot
2026-09-30 15:40 ` [PATCH BlueZ] " patchwork-bot+bluetooth
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=20260930101242.43592-1-mk02092022@gmail.com \
--to=mk02092022@gmail.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