Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 0/8] plugin/admin: Make allowlist adapter-scoped and enforce at runtime
Date: Wed, 15 Jul 2026 17:00:10 +0000	[thread overview]
Message-ID: <178413481088.415350.6996338348568524976.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260715090206.212130-1-frederic.danis@collabora.com>

Hello:

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

On Wed, 15 Jul 2026 11:01:58 +0200 you wrote:
> This series tightens AdminPolicy ServiceAllowList handling and makes
> its behavior consistent across adapter selection, adapter profile
> activation, local SDP service registration, and device service
> allowance checks.
> 
> The first part removes global AdminPolicy state and makes policy
> tracking per-adapter, which fixes D-Bus updates being emitted on the
> wrong adapter and avoids cross-adapter coupling.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2,1/8] plugins/admin: make AdminPolicy state per-adapter
    (no matching commit)
  - [BlueZ,v2,2/8] client/bluetoothctl: make admin.allow controller-aware
    (no matching commit)
  - [BlueZ,v2,3/8] doc: document admin.allow optional controller argument
    (no matching commit)
  - [BlueZ,v2,4/8] src/adapter: enforce allowlist for local services
    (no matching commit)
  - [BlueZ,v2,5/8] plugins/admin: reapply allowlist on policy updates
    (no matching commit)
  - [BlueZ,v2,6/8] doc: describe admin allowlist runtime enforcement
    (no matching commit)
  - [BlueZ,v2,7/8] profiles/audio: fix UAF on external media service teardown
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7482aceece70
  - [BlueZ,v2,8/8] device: apply profile-aware admin allowlist checks for device services
    (no matching commit)

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-07-15 17:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15  9:01 [PATCH BlueZ v2 0/8] plugin/admin: Make allowlist adapter-scoped and enforce at runtime Frédéric Danis
2026-07-15  9:01 ` [PATCH BlueZ v2 1/8] plugins/admin: make AdminPolicy state per-adapter Frédéric Danis
2026-07-15 10:16   ` plugin/admin: Make allowlist adapter-scoped and enforce at runtime bluez.test.bot
2026-07-15  9:02 ` [PATCH BlueZ v2 2/8] client/bluetoothctl: make admin.allow controller-aware Frédéric Danis
2026-07-15  9:02 ` [PATCH BlueZ v2 3/8] doc: document admin.allow optional controller argument Frédéric Danis
2026-07-15 13:40   ` Luiz Augusto von Dentz
2026-07-15 15:59     ` Frédéric Danis
2026-07-15  9:02 ` [PATCH BlueZ v2 4/8] src/adapter: enforce allowlist for local services Frédéric Danis
2026-07-15  9:02 ` [PATCH BlueZ v2 5/8] plugins/admin: reapply allowlist on policy updates Frédéric Danis
2026-07-15  9:02 ` [PATCH BlueZ v2 6/8] doc: describe admin allowlist runtime enforcement Frédéric Danis
2026-07-15  9:02 ` [PATCH BlueZ v2 7/8] profiles/audio: fix UAF on external media service teardown Frédéric Danis
2026-07-15 13:42   ` Luiz Augusto von Dentz
2026-07-15  9:02 ` [PATCH BlueZ v2 8/8] device: apply profile-aware admin allowlist checks for device services Frédéric Danis
2026-07-15 17:00 ` 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=178413481088.415350.6996338348568524976.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /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