From: Dmitry Safonov <dima@arista.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
Dmitry Safonov <0x7f454c46@gmail.com>,
Mohammad Nassiri <mnassiri@ciena.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] selftests/net: A couple of typos fixes in key-management/rst tests
Date: Thu, 1 Feb 2024 23:37:06 +0000 [thread overview]
Message-ID: <a1ac7a6e-4447-4476-8fb7-fb5f0d7ec979@arista.com> (raw)
In-Reply-To: <44d893b4-10b0-4876-bbf7-f6a81940b300@arista.com>
On 2/1/24 22:25, Dmitry Safonov wrote:
> Hi Jakub,
>
> On 2/1/24 21:21, Jakub Kicinski wrote:
>> On Thu, 1 Feb 2024 00:50:46 +0000 Dmitry Safonov wrote:
>>> Please, let me know if there will be other issues with tcp-ao tests :)
>>>
>>> Going to work on tracepoints and some other TCP-AO stuff for net-next.
>>
>> Since you're being nice and helpful I figured I'll try testing TCP-AO
>> with debug options enabled :) (kernel/configs/debug.config and
>> kernel/configs/x86_debug.config included),
>
> Haha :)
>
>> that slows things down
>> and causes a bit of flakiness in unsigned-md5-* tests:
>>
>> https://netdev.bots.linux.dev/flakes.html?br-cnt=75&tn-needle=tcp-ao
>>
>> This has links to outputs:
>> https://netdev.bots.linux.dev/contest.html?executor=vmksft-tcp-ao-dbg&pass=0
>>
>> If it's a timing thing - FWIW we started exporting
>> KSFT_MACHINE_SLOW=yes on the slow runners.
>
> I think, I know what happens here:
>
> # ok 8 AO server (AO_REQUIRED): AO client: counter TCPAOGood increased 4
> => 6
> # ok 9 AO server (AO_REQUIRED): unsigned client
> # ok 10 AO server (AO_REQUIRED): unsigned client: counter TCPAORequired
> increased 1 => 2
> # not ok 11 AO server (AO_REQUIRED): unsigned client: Counter
> netns_ao_good was not expected to increase 7 => 8
>
> for each of tests the server listens at a new port, but re-uses the same
> namespaces+veth. If the node/machine is quite slow, I guess a segment
> might have been retransmitted and the test that initiated it had already
> finished.
> And as result, the per-namespace counters are incremented, which makes
> the test fail (IOW, the test expects all segments in ns being dropped).
>
> So, I should do one of the options:
>
> 1. relax per-namespace checks (the per-socket and per-key counters are
> checked)
> 2. unshare(net) + veth setup for each test
> 3. split the selftest on smaller ones (as they create new net-ns in
> initialization)
Actually, I think there may be an easier fix:
4. Make sure that client close()s TCP-AO first, making it twsk.
And also make sure that net-ns counters read post server's close().
Will do this, let's see if this fixes the flakiness on the netdev bot :)
> I'd probably prefer (2), albeit it slows down that slow machine even
> more, but I don't think creating 2 net-ns + veth pair per each test
> would add a lot more overhead even on some rpi board. But let's see,
> maybe I'll just go with (1) as that's really easy.
>
> I'll cook a patch this week.
Thanks,
Dmitry
next prev parent reply other threads:[~2024-02-01 23:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 3:51 Dmitry Safonov
2024-01-30 3:51 ` [PATCH v2 1/3] selftests/net: Argument value mismatch when calling verify_counters() Dmitry Safonov
2024-01-30 3:51 ` [PATCH v2 2/3] selftests/net: Rectify key counters checks Dmitry Safonov
2024-01-30 3:51 ` [PATCH v2 3/3] selftests/net: Repair RST passive reset selftest Dmitry Safonov
2024-02-01 0:36 ` [PATCH v2 0/3] selftests/net: A couple of typos fixes in key-management/rst tests Jakub Kicinski
2024-02-01 0:50 ` Dmitry Safonov
2024-02-01 21:21 ` Jakub Kicinski
2024-02-01 22:25 ` Dmitry Safonov
2024-02-01 23:37 ` Dmitry Safonov [this message]
2024-02-02 2:30 ` Dmitry Safonov
2024-02-02 3:13 ` Jakub Kicinski
2024-02-01 0:40 ` 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=a1ac7a6e-4447-4476-8fb7-fb5f0d7ec979@arista.com \
--to=dima@arista.com \
--cc=0x7f454c46@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mnassiri@ciena.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.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
all inboxes | Powered by JetHome®