From: Thomas Haller <thaller@redhat.com>
To: Florian Westphal <fw@strlen.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Phil Sutter <phil@nwl.cc>, Eric Garver <eric@garver.life>,
netfilter-devel@vger.kernel.org
Subject: Re: [nf-next PATCH] netfilter: nf_tables: Support updating table's owner flag
Date: Wed, 13 Dec 2023 18:04:14 +0100 [thread overview]
Message-ID: <2bd5377971bd949474bfde9357a6a9c009cf693d.camel@redhat.com> (raw)
In-Reply-To: <20231213164554.GE27081@breakpoint.cc>
On Wed, 2023-12-13 at 17:45 +0100, Florian Westphal wrote:
> 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.
With "tables owned by somebody else", I meant to be logically owned by
firewalld (while not having NFT_TABLE_F_OWNER flag). Sorry for being
unclear.
>
> > 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.
>
I see. Thanks.
Thomas
prev parent reply other threads:[~2023-12-13 17:04 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
2023-12-13 17:04 ` Thomas Haller [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=2bd5377971bd949474bfde9357a6a9c009cf693d.camel@redhat.com \
--to=thaller@redhat.com \
--cc=eric@garver.life \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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