public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 v1] bass: Fix crash if setup is freed before bass_bcode_req response
Date: Fri, 13 Feb 2026 20:20:05 +0000	[thread overview]
Message-ID: <177101400582.2543989.11102095288331910222.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260212205710.1690782-1-luiz.dentz@gmail.com>

Hello:

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

On Thu, 12 Feb 2026 15:57:10 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> If a the stream is set to idle (e.g. because the endpoint is
> unregistered) the bass_bcode_req would be left with a dangling
> pointer possibly leading to a crash if the remote peer respond or
> the request times out.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1] bass: Fix crash if setup is freed before bass_bcode_req response
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fe0501126ba5

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



      parent reply	other threads:[~2026-02-13 20:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 20:57 [PATCH BlueZ v1] bass: Fix crash if setup is freed before bass_bcode_req response Luiz Augusto von Dentz
2026-02-12 21:50 ` [BlueZ,v1] " bluez.test.bot
2026-02-13 20: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=177101400582.2543989.11102095288331910222.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox