From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
shuah@kernel.org, cpaasch@apple.com, fw@strlen.de,
dcaratti@redhat.com, kishen.maloor@intel.com,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net 0/8] selftests: mptcp: skip tests not supported by old kernels (part 1)
Date: Tue, 30 May 2023 11:50:22 +0000 [thread overview]
Message-ID: <168544742274.5689.17805805293315572360.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230528-upstream-net-20230528-mptcp-selftests-support-old-kernels-part-1-v1-0-a32d85577fc6@tessares.net>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 28 May 2023 19:35:25 +0200 you wrote:
> After a few years of increasing test coverage in the MPTCP selftests, we
> realised [1] the last version of the selftests is supposed to run on old
> kernels without issues.
>
> Supporting older versions is not that easy for this MPTCP case: these
> selftests are often validating the internals by checking packets that
> are exchanged, when some MIB counters are incremented after some
> actions, how connections are getting opened and closed in some cases,
> etc. In other words, it is not limited to the socket interface between
> the userspace and the kernelspace. In addition, the current selftests
> run a lot of different sub-tests but the TAP13 protocol used in the
> selftests don't support sub-tests: in other words, one failure in
> sub-tests implies that the whole selftest is seen as failed at the end
> because sub-tests are not tracked. It is then important to skip
> sub-tests not supported by old kernels.
>
> [...]
Here is the summary with links:
- [net,1/8] selftests: mptcp: join: avoid using 'cmp --bytes'
https://git.kernel.org/netdev/net/c/d328fe870674
- [net,2/8] selftests: mptcp: connect: skip if MPTCP is not supported
https://git.kernel.org/netdev/net/c/d83013bdf90a
- [net,3/8] selftests: mptcp: pm nl: skip if MPTCP is not supported
https://git.kernel.org/netdev/net/c/0f4955a40daf
- [net,4/8] selftests: mptcp: join: skip if MPTCP is not supported
https://git.kernel.org/netdev/net/c/715c78a82e00
- [net,5/8] selftests: mptcp: diag: skip if MPTCP is not supported
https://git.kernel.org/netdev/net/c/46565acdd29f
- [net,6/8] selftests: mptcp: simult flows: skip if MPTCP is not supported
https://git.kernel.org/netdev/net/c/9161f21c74a1
- [net,7/8] selftests: mptcp: sockopt: skip if MPTCP is not supported
https://git.kernel.org/netdev/net/c/cf6f0fda7af7
- [net,8/8] selftests: mptcp: userspace pm: skip if MPTCP is not supported
https://git.kernel.org/netdev/net/c/63212608a92a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-05-30 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 17:35 [PATCH net 0/8] selftests: mptcp: skip tests not supported by old kernels (part 1) Matthieu Baerts
2023-05-28 17:35 ` [PATCH net 1/8] selftests: mptcp: join: avoid using 'cmp --bytes' Matthieu Baerts
2023-05-28 17:35 ` [PATCH net 2/8] selftests: mptcp: connect: skip if MPTCP is not supported Matthieu Baerts
2023-05-28 17:35 ` [PATCH net 3/8] selftests: mptcp: pm nl: " Matthieu Baerts
2023-05-28 17:35 ` [PATCH net 4/8] selftests: mptcp: join: " Matthieu Baerts
2023-05-28 17:35 ` [PATCH net 5/8] selftests: mptcp: diag: " Matthieu Baerts
2023-05-28 17:35 ` [PATCH net 6/8] selftests: mptcp: simult flows: " Matthieu Baerts
2023-05-28 17:35 ` [PATCH net 7/8] selftests: mptcp: sockopt: " Matthieu Baerts
2023-05-28 17:35 ` [PATCH net 8/8] selftests: mptcp: userspace pm: " Matthieu Baerts
2023-05-30 11:50 ` patchwork-bot+netdevbpf [this message]
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=168544742274.5689.17805805293315572360.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cpaasch@apple.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kishen.maloor@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=stable@vger.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