From: Matthieu Baerts <matttbe@kernel.org>
To: netdev-bot+sashiko@kernel.org
Cc: martineau@kernel.org, geliang@kernel.org, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, cpaasch@openai.com, netdev@vger.kernel.org,
mptcp@lists.linux.dev, linux-kernel@vger.kernel.org,
liuhangbin@kylinos.cn, shuah@kernel.org,
linux-kselftest@vger.kernel.org, bpf@vger.kernel.org,
Hangbin Liu <hangbin.liu@linux.dev>
Subject: Re: [PATCH net-next 3/4] selftests: mptcp: convert iptables to nftables for mptcp_sockopt.sh
Date: Thu, 15 Oct 2026 16:01:13 +0200 [thread overview]
Message-ID: <a3bd583f-f942-4636-8057-593357f10ec0@kernel.org> (raw)
In-Reply-To: <179201140828.434549.10971881913720826839@kernel.org>
On 14/10/2026 22:56, netdev-bot+sashiko@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found more severe
> issue(s) in other patches of this series. This mail is only an FYI, in case
> you want to address the nit picks below when you respin.
>
> Low priority / nit picks for your consideration:
>
> - [Low] The commit message does not mention two new runtime requirements
> added by this patch.
(...)
>> diff --git a/tools/testing/selftests/net/mptcp/mptcp_sockopt.sh b/tools/testing/selftests/net/mptcp/mptcp_sockopt.sh
>> index e850a87429b61..ef2738720e249 100755
>> --- a/tools/testing/selftests/net/mptcp/mptcp_sockopt.sh
>> +++ b/tools/testing/selftests/net/mptcp/mptcp_sockopt.sh
>
> [ ... ]
>
>> @@ -105,32 +109,31 @@ cleanup()
>>
>> mptcp_lib_check_mptcp
>> mptcp_lib_check_kallsyms
>> -mptcp_lib_check_tools ip "${iptables}" "${ip6tables}"
>> +mptcp_lib_check_tools ip nft jq
>
> [Severity: Low]
> This isn't a bug, but should the commit message list the new runtime
> requirements? The script now needs jq and an nft built with JSON support
> (nft -j list ruleset). The shared mptcp_lib_check_tools() helper in
> mptcp_lib.sh also gets new "nft" and "jq" cases.
>
> The commit message only says:
>
> After conversion, the generated output matches the original
> iptables/ip6tables behavior.
>
> The reason for using JSON and jq appears only in the v2 notes below the
> --- line, and those notes are dropped when the patch is applied.
>
> This check runs at top level, before any subtest. So a system that has
> iptables but no jq, or an nft without JSON support, now skips the whole
> script. That includes do_mptcp_sockopt_tests and do_tcpinq_tests, which
> don't use netfilter.
>
> Could the commit message mention the jq and nft JSON dependencies and the
> mptcp_lib.sh change?
nft is implicit. 'jq' is used in many other selftests. No need to
re-spin (but if we do, yes we can mention it just to please Clashiko).
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-10-15 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 17:56 [PATCH net-next 0/4] mptcp: misc improvements for v7.4 Matthieu Baerts (NGI0)
2026-10-13 17:56 ` [PATCH net-next 1/4] mptcp: options: mpc: avoid printing uninit data Matthieu Baerts (NGI0)
2026-10-13 17:56 ` [PATCH net-next 2/4] mptcp: options: dss: avoid printing uninit csum Matthieu Baerts (NGI0)
2026-10-13 17:56 ` [PATCH net-next 3/4] selftests: mptcp: convert iptables to nftables for mptcp_sockopt.sh Matthieu Baerts (NGI0)
2026-10-14 20:56 ` netdev-bot+sashiko
2026-10-15 14:01 ` Matthieu Baerts [this message]
2026-10-13 17:56 ` [PATCH net-next 4/4] selftests: mptcp: convert iptables to nftables for mptcp_join.sh Matthieu Baerts (NGI0)
2026-10-14 20:56 ` netdev-bot+sashiko
2026-10-15 14:01 ` Matthieu Baerts
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=a3bd583f-f942-4636-8057-593357f10ec0@kernel.org \
--to=matttbe@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cpaasch@openai.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=geliang@kernel.org \
--cc=hangbin.liu@linux.dev \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@kylinos.cn \
--cc=martineau@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev-bot+sashiko@kernel.org \
--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