From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 598f9a: transport: Preserve Release on late BAP ready
Date: Fri, 18 Sep 2026 15:25:21 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1168994/000000-a2d345@github.com> (raw)
Branch: refs/heads/1168994
Home: https://github.com/bluez/bluez
Commit: 598f9acc24f918a4b931c5c5d96937f91599b50d
https://github.com/bluez/bluez/commit/598f9acc24f918a4b931c5c5d96937f91599b50d
Author: Derek Tern <1263187-dt@users.noreply.gitlab.freedesktop.org>
Date: 2026-09-18 (Fri, 18 Sep 2026)
Changed paths:
M profiles/audio/transport.c
Log Message:
-----------
transport: Preserve Release on late BAP ready
A late stream-ready event can reach bap_resume_complete() after Release
has queued Disable. It then replies to Release with an Acquire payload
and drops the Disable request ID. Client disconnection can subsequently
free the owner while the Disable callback still refers to it.
Only complete pending Acquire/TryAcquire requests from this path. Leave
Release and its request ID for the Disable callback or cancellation.
Commit: fdbf00415c15b45929bd62b48aa01f4faa26be07
https://github.com/bluez/bluez/commit/fdbf00415c15b45929bd62b48aa01f4faa26be07
Author: Derek Tern <1263187-dt@users.noreply.gitlab.freedesktop.org>
Date: 2026-09-18 (Fri, 18 Sep 2026)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
bap: Recreate stream IO after an early Enable
When reacquiring a transport, the stream can reach Enabling before its
previous CIS finishes disconnecting. Once teardown completes, IO
recreation accepts only QoS, while CIS enabling requires existing IO.
The pending Acquire consequently stalls.
Allow deferred IO recreation in Enabling too. Keep the existing CIG-busy
checks and recreate all IO before enabling CISes.
Commit: a2d3451ed0492330293fbe52e2ca31994c831dfb
https://github.com/bluez/bluez/commit/a2d3451ed0492330293fbe52e2ca31994c831dfb
Author: Derek Tern <1263187-dt@users.noreply.gitlab.freedesktop.org>
Date: 2026-09-18 (Fri, 18 Sep 2026)
Changed paths:
M doc/functional-bap.rst
M test/functional/test_bap.py
Log Message:
-----------
test: Cover BAP transport release and reacquire
Acquire both unicast transports, close their sockets and release them
through the same D-Bus owner. Require an empty Release reply so a late
ready callback cannot pass unnoticed by returning an Acquire payload.
Repeat three times with immediate, 100 ms and one-second reacquisition.
Check Acquire reply types and active transport states. Close returned
FDs even when a reply is malformed.
Compare: https://github.com/bluez/bluez/compare/598f9acc24f9%5E...a2d3451ed049
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-18 22:25 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/1168994/000000-a2d345@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