From: Alessio Faina <alessio.faina@canonical.com>
To: Andrea Mayer <andrea.mayer@uniroma2.it>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
horms@kernel.org, Shuah Khan <shuah@kernel.org>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, stefano.salsano@uniroma2.it,
hangbin.liu@linux.dev
Subject: Re: [PATCH] [net-next, v2] selftest/net: skip srv6_end_dt[4/6]_l3vpn_test.sh if vrftable not available
Date: Mon, 7 Sep 2026 11:41:15 +0200 [thread overview]
Message-ID: <ap6Gu0oRGKXcs4vg@cicciput> (raw)
In-Reply-To: <20260904202546.a888aad9efbbf113aa1db900@uniroma2.it>
On Fri, Sep 04, 2026 at 08:25:46PM +0200, Andrea Mayer wrote:
> On Thu, 3 Sep 2026 12:35:45 +0200
> Alessio Faina <alessio.faina@canonical.com> wrote:
>
> Hi Alessio,
>
> Thanks for the v2. The check looks good to me. The comments below are
> all on the commit message and on the subject.
>
> > In case iproute2 is older than version 5.11.0, released ~Feb 23, 2021,
> > the vrftable support is not available and the tests
> > contained in the following 4 test files
> > - srv6_end_dt4_l3vpn_test.sh
> > - srv6_end_dt6_l3vpn_test.sh
> > are failing in some kernel backports.
>
> Two files now, not four.
>
> > This is the result of one those tests in an unsupported environment:
> >
> > \################################################################################
> > \TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant
> > \################################################################################
> > \
> > \ TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL]
> > \
> > \ TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL]
> > \
> > \ TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL]
> > \
> > \ TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL]
> > \
> >
> > To amend this, check the current running iproute2 supports the vrftable
> > feature and, if not, just skip the entire test to avoid a failure.
>
> IMO the sentence could say what the check does: it installs a route
> with the vrftable feature, and skips the test rather than failing when
> the feature is not supported.
>
> > v2: - remove dx[4/6] tests
> > - test if vrftable is available in the installed iproute2 application
> > v1: https://patchwork.kernel.org/project/netdevbpf/patch/20260824091537.2305107-1-alessio.faina@canonical.com/
> > - initial approach by testing DT[4/6] and DX[4/6]
> > - test if DT4/DT6 are available in iproute2
> >
> > Signed-off-by: Alessio Faina <alessio.faina@canonical.com>
> > ---
> >
> > [snip]
>
> The changelog goes under the ---. checkpatch reports it too.
>
> Since the commit message needs to be revised anyway, a few nits:
>
> i) The subject came as [PATCH] [net-next, v2] instead of
> [PATCH net-next v2]. And maybe you meant selftests/net: ?
> ii) "one those tests" -> "one of those tests" ?
> iii) The backslashes in the pasted log could go, git does not remove
> them and they stay in the commit message.
>
> Ciao,
> Andrea
Hi Andrea,
Thanks a lot for the review, I will address your comments and update the patch
accordingly. A v3 will be on its way soon.
i) Yeah, definitely my fault when I exported with format-patch I didn't
merge the [PATCH] and [net-next v2] parts. I will fix that.
ii) Yes, thanks.
iii) Is interesting, checkpatch.pl is complaining about having a
list of ##### in the commit message, but adding a space in front makes
it happy. I will use that approach.
I will add the missing cc_maintainer as well as mentioned in the list of
checks.
Kind regards,
-Alessio Faina
prev parent reply other threads:[~2026-09-07 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 10:35 Alessio Faina
2026-09-04 18:25 ` Andrea Mayer
2026-09-07 9:41 ` Alessio Faina [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=ap6Gu0oRGKXcs4vg@cicciput \
--to=alessio.faina@canonical.com \
--cc=andrea.mayer@uniroma2.it \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=stefano.salsano@uniroma2.it \
/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
all inboxes | Powered by JetHome®