From: Florian Westphal <fw@strlen.de>
To: Thomas Haller <thaller@redhat.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Phil Sutter <phil@nwl.cc>, Eric Garver <eric@garver.life>,
netfilter-devel@vger.kernel.org, Florian Westphal <fw@strlen.de>
Subject: Re: [nf-next PATCH] netfilter: nf_tables: Support updating table's owner flag
Date: Wed, 13 Dec 2023 17:45:54 +0100 [thread overview]
Message-ID: <20231213164554.GE27081@breakpoint.cc> (raw)
In-Reply-To: <17fbf1879c790d2dd59ec6367d01002b5d3b5f3a.camel@redhat.com>
Thomas Haller <thaller@redhat.com> wrote:
> Isn't the problem to solve that `nft flush ruleset` deletes tables
> owned by somebody else (firewalld)?
If they are 'owned', then no, they are not flushed, thats one of the
points of the owner thing.
> A "persist" flag sounds like a good solution. It would just have
> informational value (for user space) to be skipped by `nft flush
> ruleset`.
'flush' doesn't pass the to-be deleted tables to the kernel, so
this cannot be implemented via informational tags in userspace.
next prev parent reply other threads:[~2023-12-13 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 13:01 [nf-next PATCH] netfilter: nf_tables: Support updating table's owner flag Phil Sutter
2023-12-12 13:08 ` Pablo Neira Ayuso
2023-12-12 16:23 ` Phil Sutter
2023-12-12 22:47 ` Eric Garver
2023-12-13 12:13 ` Phil Sutter
2023-12-13 14:08 ` Eric Garver
2023-12-13 15:29 ` Florian Westphal
2023-12-13 15:15 ` Pablo Neira Ayuso
2023-12-13 15:51 ` Phil Sutter
2023-12-13 15:54 ` Pablo Neira Ayuso
2023-12-13 16:32 ` Thomas Haller
2023-12-13 16:45 ` Florian Westphal [this message]
2023-12-13 17:04 ` Thomas Haller
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=20231213164554.GE27081@breakpoint.cc \
--to=fw@strlen.de \
--cc=eric@garver.life \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=thaller@redhat.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.