From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v3 1/5] bass: Fix possible crash on bass_update_bis_sync
Date: Tue, 30 Jun 2026 20:32:45 +0000 [thread overview]
Message-ID: <178285156563.267316.16319028944884888824.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260629142649.966025-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 29 Jun 2026 10:26:45 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> bass_update_bis_sync does use bass_remove_bis which may end up
> removing the current entry causing a crash on entry->next, to avoid
> that prefetch the next entry.
> ---
> profiles/audio/bass.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
Here is the summary with links:
- [BlueZ,v3,1/5] bass: Fix possible crash on bass_update_bis_sync
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=27a4c48b0481
- [BlueZ,v3,2/5] shared/bap: Check if stream is valid before attempting to release
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2262e3715649
- [BlueZ,v3,3/5] shared/bap: Don't transition to IDLE inside bap_bcast_set_state
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c0fec57e9fa2
- [BlueZ,v3,4/5] shared/bap: Use queue_foreach to notify state changes
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a9b6c8a2ea62
- [BlueZ,v3,5/5] shared/bap: Protect bap_stream_notify_connecting
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a2c7bc03b759
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-30 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 14:26 [PATCH BlueZ v3 1/5] bass: Fix possible crash on bass_update_bis_sync Luiz Augusto von Dentz
2026-06-29 14:26 ` [PATCH BlueZ v3 2/5] shared/bap: Check if stream is valid before attempting to release Luiz Augusto von Dentz
2026-06-29 14:26 ` [PATCH BlueZ v3 3/5] shared/bap: Don't transition to IDLE inside bap_bcast_set_state Luiz Augusto von Dentz
2026-06-29 14:26 ` [PATCH BlueZ v3 4/5] shared/bap: Use queue_foreach to notify state changes Luiz Augusto von Dentz
2026-06-29 17:37 ` [BlueZ,v3,1/5] bass: Fix possible crash on bass_update_bis_sync bluez.test.bot
2026-06-30 20:32 ` 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=178285156563.267316.16319028944884888824.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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.