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 v4 0/8] net/selftests: TCP-AO selftests updates
Date: Tue, 27 Aug 2024 14:10:41 -0700 [thread overview]
Message-ID: <20240827141041.0c815dbd@kernel.org> (raw)
In-Reply-To: <20240823-tcp-ao-selftests-upd-6-12-v4-0-05623636fe8c@gmail.com>
On Fri, 23 Aug 2024 23:04:50 +0100 Dmitry Safonov via B4 Relay wrote:
> First 3 patches are more-or-less cleanups/preparations.
>
> Patches 4/5 are fixes for netns file descriptors leaks/open.
>
> Patch 6 was sent to me/contributed off-list by Mohammad, who wants 32-bit
> kernels to run TCP-AO.
>
> Patch 7 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.
>
> And the biggest change is adding TCP-AO tracepoints to selftests.
> I think it's a good addition by the following reasons:
> - The related tracepoints are now tested;
> - It allows tcp-ao selftests to raise expectations on the kernel
> behavior - up from the syscalls exit statuses + net counters.
> - Provides tracepoints usage samples.
Looks like we got no flakes over the weekend, so applying, thanks! :)
next prev parent reply other threads:[~2024-08-27 21:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 22:04 [PATCH net-next v4 0/8] net/selftests: TCP-AO selftests updates Dmitry Safonov
2024-08-23 22:04 ` Dmitry Safonov via B4 Relay
2024-08-23 22:04 ` [PATCH net-next v4 1/8] selftests/net: Clean-up double assignment Dmitry Safonov
2024-08-23 22:04 ` Dmitry Safonov via B4 Relay
2024-08-23 22:04 ` [PATCH net-next v4 2/8] selftests/net: Provide test_snprintf() helper Dmitry Safonov
2024-08-23 22:04 ` Dmitry Safonov via B4 Relay
2024-08-23 22:04 ` [PATCH net-next v4 3/8] selftests/net: Be consistent in kconfig checks Dmitry Safonov
2024-08-23 22:04 ` Dmitry Safonov via B4 Relay
2024-08-23 22:04 ` [PATCH net-next v4 4/8] selftests/net: Open /proc/thread-self in open_netns() Dmitry Safonov
2024-08-23 22:04 ` Dmitry Safonov via B4 Relay
2024-08-23 22:04 ` [PATCH net-next v4 5/8] selftests/net: Don't forget to close nsfd after switch_save_ns() Dmitry Safonov
2024-08-23 22:04 ` Dmitry Safonov via B4 Relay
2024-08-23 22:04 ` [PATCH net-next v4 6/8] selftests/tcp_ao: Fix printing format for uint64_t Dmitry Safonov
2024-08-23 22:04 ` Dmitry Safonov via B4 Relay
2024-08-23 22:04 ` [PATCH net-next v4 7/8] selftests/net: Synchronize client/server before counters checks Dmitry Safonov
2024-08-23 22:04 ` Dmitry Safonov via B4 Relay
2024-08-23 22:04 ` [PATCH net-next v4 8/8] selftests/net: Add trace events matching to tcp_ao Dmitry Safonov
2024-08-23 22:04 ` Dmitry Safonov via B4 Relay
2024-08-27 21:10 ` Jakub Kicinski [this message]
2024-08-27 22:10 ` [PATCH net-next v4 0/8] net/selftests: TCP-AO selftests updates Dmitry Safonov
2024-08-27 21:20 ` 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=20240827141041.0c815dbd@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.