Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Iaroslav Voitovych <yaroslav.voytovych@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] emulator: Free hooks in btdev_destroy
Date: Mon, 12 Oct 2026 21:50:06 +0000	[thread overview]
Message-ID: <179184180676.4115061.4860406922959655412.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261010031846.2842837-1-yaroslav.voytovych@gmail.com>

Hello:

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

On Sat, 10 Oct 2026 05:18:46 +0200 you wrote:
> Hooks added with btdev_add_hook() are only freed by btdev_del_hook(),
> so a hook still installed when the device is destroyed is leaked. Five
> mgmt-tester cases leave one installed: "Add + Remove Device Nowait -
> Success" and the four "Adv. (non-)connectable & connected" cases on the
> LE emulator; one l2cap-tester case does too. They pass, but with ASan
> the tester exits with status 1 because LeakSanitizer reports, for
> mgmt-tester:
> 
> [...]

Here is the summary with links:
  - [BlueZ] emulator: Free hooks in btdev_destroy
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8da7e648a9fb

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-10-12 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10  3:18 [PATCH BlueZ] emulator: Free hooks in btdev_destroy Iaroslav Voitovych
2026-10-10  9:42 ` [BlueZ] " bluez.test.bot
2026-10-12 21:50 ` 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=179184180676.4115061.4860406922959655412.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=yaroslav.voytovych@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