[bluez/bluez] e1ea74: transport: Preserve Release on late BAP ready

["github-actions[bot]" <noreply@github.com>]

  Branch: refs/heads/1180235
  Home:   https://github.com/bluez/bluez
  Commit: e1ea7423ea3be02338e514bca16a01e3973dcb88
      https://github.com/bluez/bluez/commit/e1ea7423ea3be02338e514bca16a01e3973dcb88
  Author: Derek Tern <1263187-dt@users.noreply.gitlab.freedesktop.org>
  Date:   2026-10-06 (Tue, 06 Oct 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.

Fixes: 466fce0209a3 ("transport: handle BAP Enabling state correctly when resuming")
Assisted-by: Codex:GPT-6


  Commit: df5d17697e7302f379efff4fb34017a0f7f68a1f
      https://github.com/bluez/bluez/commit/df5d17697e7302f379efff4fb34017a0f7f68a1f
  Author: Derek Tern <1263187-dt@users.noreply.gitlab.freedesktop.org>
  Date:   2026-10-06 (Tue, 06 Oct 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.

Fixes: 7feff47a9fbe ("bap: delay QoS & IO creation if CIG is busy or setups configuring")
Assisted-by: Codex:GPT-6


  Commit: 2e68607f4261540a66453cd68d67b0bc13ab6317
      https://github.com/bluez/bluez/commit/2e68607f4261540a66453cd68d67b0bc13ab6317
  Author: Derek Tern <1263187-dt@users.noreply.gitlab.freedesktop.org>
  Date:   2026-10-06 (Tue, 06 Oct 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.

Wait for both Acquire replies before Release, and for both Release
replies before the next Acquire. Only requests on different transport
paths are concurrent; no path has successive operations queued without
waiting for its preceding reply.

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.

Assisted-by: Codex:GPT-6


Compare: https://github.com/bluez/bluez/compare/e1ea7423ea3b%5E...2e68607f4261

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications