All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] bap: tolerate inverted STREAMING and iso_connect_cb()
Date: Mon, 20 Oct 2025 13:20:07 +0000	[thread overview]
Message-ID: <176096640799.201781.1405336622138403931.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <d442c20f47eb10f51c19480988964e881f6b0049.1760542606.git.pav@iki.fi>

Hello:

This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Wed, 15 Oct 2025 18:40:11 +0300 you wrote:
> 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.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/2] bap: tolerate inverted STREAMING and iso_connect_cb()
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c584335d4436
  - [BlueZ,2/2] transport: wait until BAP fd is writable/readable before resuming
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=bac077c96b67

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-10-20 13:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 15:40 [PATCH BlueZ 1/2] bap: tolerate inverted STREAMING and iso_connect_cb() Pauli Virtanen
2025-10-15 15:40 ` [PATCH BlueZ 2/2] transport: wait until BAP fd is writable/readable before resuming Pauli Virtanen
2025-10-15 17:35 ` [BlueZ,1/2] bap: tolerate inverted STREAMING and iso_connect_cb() bluez.test.bot
2025-10-20 13:20 ` patchwork-bot+bluetooth [this message]

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=176096640799.201781.1405336622138403931.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.