From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, David Riley <d.riley@proxmox.com>
Subject: applied: [PATCH access-control/network v6 0/8] fix #7520: sdn: prune orphaned ACLs and handle VNet migrations
Date: Mon, 2 Nov 2026 23:51:52 +0100 [thread overview]
Message-ID: <179365989933.2007812.8207392472603374220.b4-ty@b4> (raw)
In-Reply-To: <20260716104247.29047-1-d.riley@proxmox.com>
On Thu, 16 Jul 2026 12:42:39 +0200, David Riley wrote:
> Thanks @Stefan H. for the review and testing.
>
> Difference from v5:
> * Use the running_config helper.
> * Add a refactor commit for the compile_running_cfg to also use the
> running_config helper.
> * The comment for find_acl_tree_node_parent now uses the POD format.
> * Remove 'use strict;' and 'use warning;' in the pruning and
> migration test as this is implied by 'use v5.36'
> * Update the warning message in the migration logic to reflect the
> behaviour of the actual check.
>
> [...]
Applied, thanks!
[pve-access-control] applied to git/pve-access-control.git (master)
[1/6] permission: add acl tree node parent lookup without node creation
commit: c8cf60e4a507439ec395cb4d8782f3b4c32d5f23
[2/6] fix #7520: sdn: add pruning SDN resources ACLs
commit: 1ccee88350f8d62cdb795f624d6e17bdfdb1164b
[3/6] test: add sdn acl pruning tests
commit: 6474d0910dcdd24f83e48d2d75cf37949bfb07c3
[4/6] permission: add helper to check for active permissions
commit: a1e9f47871f3fea3991d2b0a80e05557ad788dfd
[5/6] fix #7520: sdn: add VNet ACL migration
commit: 8b4b22878922dd4121b3f102406d6a51d8744827
[6/6] test: add sdn acl migration tests
commit: 7fbd23d09e2e19f05c559214afe73c4078dc705b
[pve-network] applied to git/pve-network.git (master)
[1/2] sdn: refactor compile_running_cfg to use running_config helper
commit: 78eca6bb6ef85ab4fdaf4e53bce5970bc59fcecb
[2/2] fix #7520: config: prune orphaned and relocate moved VNet ACLs
commit: 802dc9cae7fc8704a30bcdf2c280cf51ef1d79a8
prev parent reply other threads:[~2026-11-02 22:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 10:42 [PATCH access-control/network v6 0/8] fix #7520: sdn: prune orphaned ACLs and handle VNet migrations David Riley
2026-07-16 10:42 ` [PATCH pve-access-control v6 1/8] permission: add acl tree node parent lookup without node creation David Riley
2026-07-16 10:42 ` [PATCH pve-access-control v6 2/8] fix #7520: sdn: add pruning SDN resources ACLs David Riley
2026-07-16 10:42 ` [PATCH pve-access-control v6 3/8] test: add sdn acl pruning tests David Riley
2026-07-16 10:42 ` [PATCH pve-access-control v6 4/8] permission: add helper to check for active permissions David Riley
2026-07-16 10:42 ` [PATCH pve-access-control v6 5/8] fix #7520: sdn: add VNet ACL migration David Riley
2026-07-16 10:42 ` [PATCH pve-access-control v6 6/8] test: add sdn acl migration tests David Riley
2026-07-16 10:42 ` [PATCH pve-network v6 7/8] sdn: refactor compile_running_cfg to use running_config helper David Riley
2026-07-16 10:42 ` [PATCH pve-network v6 8/8] fix #7520: config: prune orphaned and relocate moved VNet ACLs David Riley
2026-09-09 11:58 ` [PATCH access-control/network v6 0/8] fix #7520: sdn: prune orphaned ACLs and handle VNet migrations David Riley
2026-11-02 22:51 ` Thomas Lamprecht [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=179365989933.2007812.8207392472603374220.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=d.riley@proxmox.com \
--cc=pve-devel@lists.proxmox.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