From: patchwork-bot+bluetooth@kernel.org
To: Pavel Bozhko <pvbozhko@salutedevices.com>
Cc: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] advertising: Fix double-free in client_free
Date: Mon, 16 Nov 2026 20:00:12 +0000 [thread overview]
Message-ID: <179485921202.3860040.16430372342970958452.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261113092759.24927-1-pvbozhko@salutedevices.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 13 Nov 2026 12:27:59 +0300 you wrote:
> Unregister, disconnect and a failed RegisterAdvertisement can each
> queue client_free() from idle. The second g_free(client->owner) aborts
> bluetoothd. Freeing the client directly while that idle is still
> pending lets the callback run after the client is gone.
>
> Remember the g_idle_add() id and do not queue another free while it is
> set. Drop the idle source when the client is freed directly.
>
> [...]
Here is the summary with links:
- [BlueZ,v2] advertising: Fix double-free in client_free
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=de977a4eb953
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-11-16 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 17:03 [RFC PATCH BlueZ 0/1] advertising: Fix double-free in client_free Pavel Bozhko
2026-11-12 17:03 ` [RFC PATCH BlueZ 1/1] " Pavel Bozhko
2026-11-12 17:33 ` Luiz Augusto von Dentz
2026-11-13 9:27 ` [PATCH BlueZ v2] " Pavel Bozhko
2026-11-16 20:00 ` patchwork-bot+bluetooth [this message]
2026-11-13 3:33 ` bluez.test.bot
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=179485921202.3860040.16430372342970958452.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=pvbozhko@salutedevices.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