From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Thomas Haller <thaller@redhat.com>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] tests: shell: flush ruleset with -U after feature probing
Date: Wed, 6 Dec 2023 13:14:53 +0100 [thread overview]
Message-ID: <ZXBlvcV3jUfJCnMs@calendula> (raw)
In-Reply-To: <80b4cbbb54cf17a83ccbadaa3cd194790f87f67f.camel@redhat.com>
On Wed, Dec 06, 2023 at 07:47:44AM +0100, Thomas Haller wrote:
> On Tue, 2023-12-05 at 20:29 +0100, Florian Westphal wrote:
> > Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > > feature probe script leave a ruleset in place, flush it once
> > > probing is
> > > complete.
> >
> > Perhaps change feature_probe() to always use 'unshare -n'?
>
> feature_probe already uses unshare, unless the caller opts out of it.
I am opting out with -I as the patch title specifies.
> Maybe don't do that.
>
> > Some scripts also create netdevices.
>
> Some tests also create netdevices and may not clean them up properly.
> It's even desirable that tests don't clean them up, because it removes
> boilerplate from tests. But more importantly: not deleting those
> devices leaves a certain state after the test, that can be checked by
> `.nft`/`.json-nft` dumps.
I see, those were not a problem for me when running -U so far.
> The mode without unshare exists for historic reasons, as unshare was
> added initially. At this point, what is the use of supporting or using
> that?
This provides an easy way for me to test 'nft monitor'.
I can keep it out of tree if you prefer -U remains broken.
next prev parent reply other threads:[~2023-12-06 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 15:43 [PATCH nft] tests: shell: flush ruleset with -U after feature probing Pablo Neira Ayuso
2023-12-05 19:29 ` Florian Westphal
2023-12-06 6:47 ` Thomas Haller
2023-12-06 12:14 ` Pablo Neira Ayuso [this message]
2023-12-06 12:18 ` Florian Westphal
2023-12-06 12:33 ` Pablo Neira Ayuso
2023-12-06 12:49 ` Pablo Neira Ayuso
2023-12-06 12:52 ` Florian Westphal
2023-12-06 13:12 ` Thomas Haller
2023-12-06 12:45 ` Thomas Haller
2023-12-06 12:57 ` Pablo Neira Ayuso
2023-12-06 12:29 ` Pablo Neira Ayuso
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=ZXBlvcV3jUfJCnMs@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--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.