From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] tests/shell: Restore testcases/sets/0036add_set_element_expiration_0
Date: Thu, 29 Oct 2020 12:18:24 +0100 [thread overview]
Message-ID: <20201029111824.GV13016@orbyte.nwl.cc> (raw)
In-Reply-To: <20201028190847.GA4360@salvia>
Hi Pablo,
On Wed, Oct 28, 2020 at 08:08:47PM +0100, Pablo Neira Ayuso wrote:
> On Wed, Oct 28, 2020 at 08:05:38PM +0100, Pablo Neira Ayuso wrote:
> > Hi Phil,
> >
> > On Wed, Oct 28, 2020 at 06:03:38PM +0100, Phil Sutter wrote:
> > > This reverts both commits 46b54fdcf266d3d631ffb6102067825d7672db46 and
> > > 0e258556f7f3da35deeb6d5cfdec51eafc7db80d.
> > >
> > > With both applied, the test succeeded *only* if 'nft monitor' was
> > > running in background, which is equivalent to the original problem
> > > (where the test succeeded only if *no* 'nft monitor' was running).
> > >
> > > The test merely exposed a kernel bug, so in fact it is correct.
> >
> > Please, do not revert this.
> >
> > This kernel patch needs this fix:
> >
> > https://patchwork.ozlabs.org/project/netfilter-devel/patch/20201022204032.28904-1-pablo@netfilter.org/
>
> With the kernel patch above, this test does not break anymore.
>
> ie. --echo is not printing the generation ID because kernel bug.
Oh, I mis-read the kernel patch, sorry for the mess. I would suggest to
change your test case fix into this though:
| -test_output=$($NFT -e -f - <<< "$RULESET" 2>&1 | head -n -1)
| +test_output=$($NFT -e -f - <<< "$RULESET" 2>&1 | grep -v '# new generation')
This makes it clear what is to be omitted and also makes the test work
with unpatched kernels as well. Fine with you?
Thanks, Phil
next prev parent reply other threads:[~2020-10-29 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 17:03 [nft PATCH] tests/shell: Restore testcases/sets/0036add_set_element_expiration_0 Phil Sutter
2020-10-28 19:05 ` Pablo Neira Ayuso
2020-10-28 19:08 ` Pablo Neira Ayuso
2020-10-29 11:18 ` Phil Sutter [this message]
2020-10-29 11:44 ` 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=20201029111824.GV13016@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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;
as well as URLs for NNTP newsgroup(s).