From: patchwork-bot+bluetooth@kernel.org
To: Kevin Dewald <kevin@simpleble.org>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ] advertising: Fix leaking clients that exit while registering
Date: Wed, 28 Oct 2026 13:30:05 +0000 [thread overview]
Message-ID: <179319420583.722681.1792431200395296166.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261027051206.92829-1-kevin@simpleble.org>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 26 Oct 2026 22:12:06 -0700 you wrote:
> RegisterAdvertisement allocates an instance and adds the client to the
> list ActiveInstances counts, but only watches for the client
> disconnecting once the advertisement has been added. A client that goes
> away before that, for example one that never answers GetAll on its
> advertisement object, is never removed, and its instance stays
> allocated until bluetoothd restarts. Once all instances have leaked,
> every registration fails with "Maximum advertisements reached".
>
> [...]
Here is the summary with links:
- [BlueZ] advertising: Fix leaking clients that exit while registering
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0d57c12f5aca
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-10-28 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 5:12 [PATCH BlueZ] advertising: Fix leaking clients that exit while registering Kevin Dewald
2026-10-27 8:40 ` [BlueZ] " bluez.test.bot
2026-10-28 13:30 ` 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=179319420583.722681.1792431200395296166.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=kevin@simpleble.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