From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-firewall 3/3] fix #1965: firewall: cache cluster config
Date: Wed, 4 Nov 2026 17:15:20 +0100 [thread overview]
Message-ID: <baf38240-5062-4ace-8586-1929050f4bd8@proxmox.com> (raw)
In-Reply-To: <20261104141931.399659-4-a.bied-charreton@proxmox.com>
On 11/4/26 3:20 PM, Arthur Bied-Charreton wrote:
[...]
> + # cluster.fw is not bumped on SDN changes, however a change in the SDN config may make a
> + # rule that previously failed to parse valid again, or invalidate a previously valid one.
> + # re-verify all rules if the ipsets names yielded by the current SDN config differ from the
> + # stored ones.
> + my $names = sub { join(',', sort keys(($_[0] // {})->{ipset}->%*)) };
> + my $sdn_ipsets_changed = $names->($sdn_conf) ne $names->($cluster_conf->{sdn});
> + $cluster_conf->{sdn} = $sdn_conf;
> +
> + return $cluster_conf if !$sdn_ipsets_changed;
> +
> + my $reverify = sub {
> + my ($rules, $conf, $rule_env) = @_;
> + for my $rule ($rules->@*) {
> + delete $rule->{errors};
> + verify_rule($rule, $cluster_conf, $conf, $rule_env, 1);
verify_rule can die, so we should probably eval here? Or at least in the loop below?
next prev parent reply other threads:[~2026-11-04 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 14:19 [PATCH firewall 0/3] fix #1965: cache the cluster firewall config Arthur Bied-Charreton
2026-11-04 14:19 ` [PATCH pve-firewall 1/3] firewall: run make tidy Arthur Bied-Charreton
2026-11-04 14:19 ` [PATCH pve-firewall 2/3] firewall: parser: factor out error logging Arthur Bied-Charreton
2026-11-04 14:19 ` [PATCH pve-firewall 3/3] fix #1965: firewall: cache cluster config Arthur Bied-Charreton
2026-11-04 16:15 ` Stefan Hanreich [this message]
2026-11-05 8:19 ` Arthur Bied-Charreton
2026-11-04 16:36 ` Stefan Hanreich
2026-11-05 8:15 ` Arthur Bied-Charreton
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=baf38240-5062-4ace-8586-1929050f4bd8@proxmox.com \
--to=s.hanreich@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.