From: Simon Horman <horms@kernel.org>
To: equinox@diac24.net
Cc: Simon Horman <horms@kernel.org>,
pabeni@redhat.com, kuba@kernel.org, idosch@nvidia.com,
dsahern@kernel.org, davem@davemloft.net, edumazet@google.com,
corbet@lwn.net, skhan@linuxfoundation.org, fmancera@suse.de,
lorenzo@google.com, maze@google.com, prohr@google.com,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kselftest@vger.kernel.org, furry13@gmail.com
Subject: Re: [PATCH net-next 8/9] selftests: net: RFC6724 rule 5.5 tests
Date: Tue, 21 Jul 2026 14:50:51 +0100 [thread overview]
Message-ID: <20260721135051.388459-1-horms@kernel.org> (raw)
In-Reply-To: <20260714094030.136317-9-equinox@diac24.net>
This is an AI-generated review of your patch. The human sending this
email has considered the AI review valid, or at least plausible.
https://sashiko.dev/#/patchset/20260714094030.136317-2-equinox@diac24.net?part=8
---
--- Patch [8]: [PATCH net-next 8/9] selftests: net: RFC6724 rule 5.5 tests ---
commit ae975bc04160e9173acb7759f9db7580aa0ca14e
Author: David 'equinox' Lamparter <equinox@diac24.net>
selftests: net: RFC6724 rule 5.5 tests
This commit introduces a new Python-based test script to verify IPv6 source
address selection logic, focusing on RFC6724 rule 5.5. It also enables
CONFIG_IPV6_SUBTREES in the net selftests config and wires up the script in
the Makefile.
> diff --git a/tools/testing/selftests/net/Makefile b/tools/testing/selftests/net/Makefile
> index 708d960ae07d5..c07d2aebad695 100644
> --- a/tools/testing/selftests/net/Makefile
> +++ b/tools/testing/selftests/net/Makefile
> @@ -53,6 +53,7 @@ TEST_PROGS := \
> ipv6_flowlabel.sh \
> ipv6_force_forwarding.sh \
> ipv6_route_update_soft_lockup.sh \
> + ipv6_saddr_rfc6724rule5p5.py \
> ipvtap_test.sh \
[ ... ]
> diff --git a/tools/testing/selftests/net/ipv6_saddr_rfc6724rule5p5.py b/tools/testing/selftests/net/ipv6_saddr_rfc6724rule5p5.py
> new file mode 100644
[Severity: Medium]
Since ipv6_saddr_rfc6724rule5p5.py is added to TEST_PROGS in the Makefile,
the kselftest framework expects it to be directly executable. However, it is
being created with mode 100644 instead of 100755.
Will this cause the test runner to skip the script or fail to execute it
during automated testing?
> index 0000000000000..682b39ba991da
> --- /dev/null
> +++ b/tools/testing/selftests/net/ipv6_saddr_rfc6724rule5p5.py
> @@ -0,0 +1,231 @@
> +#!/usr/bin/env python3
next prev parent reply other threads:[~2026-07-21 13:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 9:40 [PATCH net-next 0/9] RFC 6724 rule 5.5 support David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 1/9] net/ipv6: fix lookup for ::/0 (non-)subtree route David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 2/9] net/ipv6: flatten ip6_route_get_saddr David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 3/9] net/ipv6: create ipv6_fl_get_saddr David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 4/9] net/ipv6: use ipv6_fl_get_saddr in output David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 5/9] net/ipv6: drop ip6_route_get_saddr David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 6/9] net/ipv6: flip IPV6_SUBTREES default to Y David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 7/9] net/ipv6: support RFC6724 rule 5.5 via subtrees David 'equinox' Lamparter
2026-07-21 13:50 ` Simon Horman
2026-07-21 14:37 ` David 'equinox' Lamparter
2026-07-14 9:40 ` [PATCH net-next 8/9] selftests: net: RFC6724 rule 5.5 tests David 'equinox' Lamparter
2026-07-21 13:50 ` Simon Horman [this message]
2026-07-14 9:40 ` [PATCH net-next 9/9] net: document RFC6724 rule 5.5 implementation David 'equinox' Lamparter
2026-07-14 13:01 ` Jonathan Corbet
2026-07-14 17:16 ` David 'equinox' Lamparter
2026-07-14 17:31 ` Jonathan Corbet
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=20260721135051.388459-1-horms@kernel.org \
--to=horms@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=equinox@diac24.net \
--cc=fmancera@suse.de \
--cc=furry13@gmail.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lorenzo@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prohr@google.com \
--cc=skhan@linuxfoundation.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