From: Simon Horman <horms@kernel.org>
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH net] selftests: netfilter: nft_flowtable.sh: make first pass deterministic
Date: Thu, 24 Oct 2024 10:37:16 +0100 [thread overview]
Message-ID: <20241024093716.GK402847@kernel.org> (raw)
In-Reply-To: <20241022152324.13554-1-fw@strlen.de>
On Tue, Oct 22, 2024 at 05:23:18PM +0200, Florian Westphal wrote:
> The CI occasionaly encounters a failing test run. Example:
> # PASS: ipsec tunnel mode for ns1/ns2
> # re-run with random mtus: -o 10966 -l 19499 -r 31322
> # PASS: flow offloaded for ns1/ns2
> [..]
> # FAIL: ipsec tunnel ... counter 1157059 exceeds expected value 878489
>
> This script will re-exec itself, on the second run, random MTUs are
> chosen for the involved links. This is done so we can cover different
> combinations (large mtu on client, small on server, link has lowest
> mtu, etc).
>
> Furthermore, file size is random, even for the first run.
>
> Rework this script and always use the same file size on initial run so
> that at least the first round can be expected to have reproducible
> behavior.
>
> Second round will use random mtu/filesize.
>
> Raise the failure limit to that of the file size, this should avoid all
> errneous test errors. Currently, first fin will remove the offload, so if
> one peer is already closing remaining data is handled by classic path,
> which result in larger-than-expected counter and a test failure.
>
> Given packet path also counts tcp/ip headers, in case offload is
> completely broken this test will still fail (as expected).
>
> The test counter limit could be made more strict again in the future
> once flowtable can keep a connection in offloaded state until FINs
> in both directions were seen.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
> If you prefer you can also apply this to net-next instead.
Hi Florian,
No preference on my side.
But if it is for net, then we'll need a fixes tag.
Which you can simply add by responding with it to this email.
(I think it has to start at the beginning of the line.)
In any case,
Reviewed-by: Simon Horman <horms@kernel.org>
...
next prev parent reply other threads:[~2024-10-24 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 15:23 [PATCH net] selftests: netfilter: nft_flowtable.sh: make first pass deterministic Florian Westphal
2024-10-24 9:37 ` Simon Horman [this message]
2024-10-29 18:30 ` patchwork-bot+netdevbpf
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=20241024093716.GK402847@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@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.