From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 32197f: bap: tolerate inverted STREAMING and iso_connect_cb()
Date: Wed, 15 Oct 2025 08:46:34 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1011959/000000-42be56@github.com> (raw)
Branch: refs/heads/1011959
Home: https://github.com/bluez/bluez
Commit: 32197fd668cb86c0d6750cb68d51f225f993bd48
https://github.com/bluez/bluez/commit/32197fd668cb86c0d6750cb68d51f225f993bd48
Author: Pauli Virtanen <pav@iki.fi>
Date: 2025-10-15 (Wed, 15 Oct 2025)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
bap: tolerate inverted STREAMING and iso_connect_cb()
Ordering of STREAMING and iso_connect_cb() is unspecified, as
kernel/Glib do not preserve the order of these events.
STREAMING before iso_connect_cb() causes transport to fail Acquire()
since bt_bap_stream_io::connecting == true.
Fix by marking IO as connected even though the connection didn't yet
complete. The socket fd is valid, although not yet writable/readable.
Fixes: https://github.com/bluez/bluez/issues/1506
Commit: 42be568f2c1286bb0f4de833e12630af9a676bfb
https://github.com/bluez/bluez/commit/42be568f2c1286bb0f4de833e12630af9a676bfb
Author: Pauli Virtanen <pav@iki.fi>
Date: 2025-10-15 (Wed, 15 Oct 2025)
Changed paths:
M profiles/audio/transport.c
Log Message:
-----------
transport: wait until BAP fd is writable/readable before resuming
Connection may still be pending when entering STREAMING.
Wait until the fd becomes readable/writable before continuing.
Compare: https://github.com/bluez/bluez/compare/32197fd668cb%5E...42be568f2c12
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-10-15 15:46 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/1011959/000000-42be56@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).