All of lore.kernel.org
 help / color / mirror / Atom feed
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 4/4] selftests: mptcp: convert iptables to nftables for mptcp_join.sh
Date: Thu, 15 Oct 2026 16:01:28 +0200	[thread overview]
Message-ID: <59c8b34f-4cf8-4747-a884-306115c32d59@kernel.org> (raw)
In-Reply-To: <179201140983.434549.4591346402914779226@kernel.org>

On 14/10/2026 22:56, netdev-bot+sashiko@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential
> issue(s) to consider.
> 
> Critical: 0 · High: 0 · Medium: 1 · Low: 0
> 
> If you believe none of the issues are legitimate, please reply to each
> issue of Medium severity or higher and explain why the AI is wrong.
> If any of them are legitimate and you plan to respin, please let patchwork
> know by including "pw-bot: cr" as a separate line at the end of your reply
> (one such reply per series is enough).
> 
> - [Medium] mptcp_join.sh init() now calls `mptcp_lib_check_tools ip tc ss
>   nft` (mptcp_join.sh:192).

TL;DR not an issue.

> --
> 
> selftests: mptcp: convert iptables to nftables for mptcp_join.sh
> 
> This converts the iptables/ip6tables rules in mptcp_join.sh to nftables.
> The cBPF bytecode matches are replaced with native nft matching, and
> hard-coded offsets are used for RM_ADDR. The config file is updated to
> match, and the iptables/ip6tables tool check is removed from
> mptcp_lib.sh.
> 
>> diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
>> index 18ce7136a2b0e..f4d8afaeda4f3 100755
>> --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
>> +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> 
> [ ... ]
> 
>> @@ -196,7 +189,7 @@ init() {
>>  
>>  	mptcp_lib_check_mptcp
>>  	mptcp_lib_check_kallsyms
>> -	mptcp_lib_check_tools ip tc ss "${iptables}" "${ip6tables}"
>> +	mptcp_lib_check_tools ip tc ss nft
> 
> [Severity: Medium]
> Will this skip the whole mptcp_join.sh suite when nft has no JSON
> support?

Yes, but really, who has nft without JSON support? If a CI doesn't have
that, better to skip everything to be clear that something important is
missing instead of just skipping some subtests which might be unnoticed.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2026-10-15 14:01 UTC|newest]

Thread overview: 10+ 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
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 [this message]
2026-10-20  9:10 ` [PATCH net-next 0/4] mptcp: misc improvements for v7.4 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=59c8b34f-4cf8-4747-a884-306115c32d59@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 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.