From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Safonov via B4 Relay <devnull+0x7f454c46.gmail.com@kernel.org>
Cc: 0x7f454c46@gmail.com, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
Mohammad Nassiri <mnassiri@ciena.com>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/7] net/selftests: TCP-AO selftests updates
Date: Fri, 2 Aug 2024 08:18:23 -0700 [thread overview]
Message-ID: <20240802081823.67a27db3@kernel.org> (raw)
In-Reply-To: <20240802-tcp-ao-selftests-upd-6-12-v2-0-370c99358161@gmail.com>
On Fri, 02 Aug 2024 10:23:24 +0100 Dmitry Safonov via B4 Relay wrote:
> First 4 patches are more-or-less cleanups/preparations.
>
> Patch 5 was sent to me/contributed off-list by Mohammad, who wants 32-bit
> kernels to run TCP-AO.
>
> Patch 6 is a workaround/fix for slow VMs. Albeit, I can't reproduce
> the issue, but I hope it will fix netdev flakes for connect-deny-*
> tests.
Hm, could be a coincidence but we did hit:
# not ok 55 # error 381[unsigned-md5.c:24] Failed to add a VRF: -17
# not ok 56 # error 383[unsigned-md5.c:33] Failed to add a route to VRF: -22: Key was rejected by service
https://netdev-3.bots.linux.dev/vmksft-tcp-ao-dbg/results/710001/4-unsigned-md5-ipv6/stdout
in the first run after this got queued. But the retry worked:
https://netdev-3.bots.linux.dev/vmksft-tcp-ao-dbg/results/710001/4-unsigned-md5-ipv6-retry/stdout
🤷️
next prev parent reply other threads:[~2024-08-02 15:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 9:23 [PATCH net-next v2 0/7] net/selftests: TCP-AO selftests updates Dmitry Safonov
2024-08-02 9:23 ` Dmitry Safonov via B4 Relay
2024-08-02 9:23 ` [PATCH net-next v2 1/7] selftests/net: Clean-up double assignment Dmitry Safonov
2024-08-02 9:23 ` Dmitry Safonov via B4 Relay
2024-08-02 9:23 ` [PATCH net-next v2 2/7] selftests/net: Provide test_snprintf() helper Dmitry Safonov
2024-08-02 9:23 ` Dmitry Safonov via B4 Relay
2024-08-02 9:23 ` [PATCH net-next v2 3/7] selftests/net: Be consistent in kconfig checks Dmitry Safonov
2024-08-02 9:23 ` Dmitry Safonov via B4 Relay
2024-08-02 9:23 ` [PATCH net-next v2 4/7] selftests/net: Don't forget to close nsfd after switch_save_ns() Dmitry Safonov
2024-08-02 9:23 ` Dmitry Safonov via B4 Relay
2024-08-02 9:23 ` [PATCH net-next v2 5/7] selftests/tcp_ao: Fix printing format for uint64_t Dmitry Safonov
2024-08-02 9:23 ` Dmitry Safonov via B4 Relay
2024-08-02 9:23 ` [PATCH net-next v2 6/7] selftests/net: Synchronize client/server before counters checks Dmitry Safonov
2024-08-02 9:23 ` Dmitry Safonov via B4 Relay
2024-08-04 9:47 ` Simon Horman
2024-08-07 0:42 ` Dmitry Safonov
2024-08-02 9:23 ` [PATCH net-next v2 7/7] selftests/net: Add trace events matching to tcp_ao Dmitry Safonov
2024-08-02 9:23 ` Dmitry Safonov via B4 Relay
2024-08-02 15:18 ` Jakub Kicinski [this message]
2024-08-02 15:32 ` [PATCH net-next v2 0/7] net/selftests: TCP-AO selftests updates Jakub Kicinski
2024-08-03 0:50 ` Dmitry Safonov
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=20240802081823.67a27db3@kernel.org \
--to=kuba@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=davem@davemloft.net \
--cc=devnull+0x7f454c46.gmail.com@kernel.org \
--cc=edumazet@google.com \
--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 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.