The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	 Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	 Paolo Abeni <pabeni@redhat.com>,
	 Simon Horman <horms@kernel.org>,  Shuah Khan <shuah@kernel.org>,
	 netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	 Eelco Chaudron <echaudro@redhat.com>,
	 Ilya Maximets <i.maximets@ovn.org>,
	dev@openvswitch.org
Subject: Re: [PATCH net 2/7] selftests: openvswitch: add config file
Date: Thu, 16 Jul 2026 11:38:54 -0400	[thread overview]
Message-ID: <f7t5x2frlkh.fsf@redhat.com> (raw)
In-Reply-To: <20260710-net-sft-fix-containers-v1-2-a2915c294ef5@kernel.org> (Matthieu Baerts's message of "Fri, 10 Jul 2026 20:04:42 +0200")

Hi Matthieu,

"Matthieu Baerts (NGI0)" <matttbe@kernel.org> writes:

> The kselftests doc mentions that a config file should be present "if a
> test needs specific kernel config options enabled". This selftest
> requires some kernel config, but no config file was provided.
>
> We could say that a sub-target could use the parent's config file, but
> the kselftests doc doesn't mention anything about that. Plus the
> net/openvswitch target is the only net target without a config file.

We've been operating on that assumption from the openvswitch side, but
it's true that isn't explicitly documented anywhere, and I guess it
isn't officially supported in the kselftest framework.  I guess we'll
need to keep updating this config as we add tests for things like SCTP,
and others, and maybe that's a good thing like we can add a comment
describing which tests take which configs.

The downside is for most of the OVS testing we use the NIPA scripts
and those 'inherit' the parent config, so it would be a change on our
side from the development standpoint (but probably something we should
have been doing from the beginning).

That said, would it be worth also exploring the 'cascading
configuration' support?  It seems like a useful feature, but maybe it
should be a separate discussion.  I ask because of how OVS interacts
with the networking stack as an 'alternative bridge' so-to-speak, I do
worry about having to duplicate lots of configurations between the two
as we expand the test coverage on OVS side.

> Here is a new config file, which is a trimmed version of the net one,
> with hopefully the minimal required kconfig on top of 'make defconfig'.

Should this also remove the OVS configs from the upper level since there
shouldn't be OVS tests executing there (ie: CONFIG_OPENVSWITCH*)?

> The Fixes tag points to the introduction of the net/openvswitch target,
> just to help validating this target on stable kernels.
>
> Fixes: 25f16c873fb1 ("selftests: add openvswitch selftest suite")
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> ---
> To: Aaron Conole <aconole@redhat.com>
> To: Eelco Chaudron <echaudro@redhat.com>
> To: Ilya Maximets <i.maximets@ovn.org>
> Cc: dev@openvswitch.org
> ---
>  tools/testing/selftests/net/openvswitch/config | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
>
> diff --git a/tools/testing/selftests/net/openvswitch/config b/tools/testing/selftests/net/openvswitch/config
> new file mode 100644
> index 000000000000..c659749cd086
> --- /dev/null
> +++ b/tools/testing/selftests/net/openvswitch/config
> @@ -0,0 +1,16 @@
> +CONFIG_GENEVE=m
> +CONFIG_INET_DIAG=y
> +CONFIG_IPV6=y
> +CONFIG_NETFILTER=y
> +CONFIG_NET_IPGRE=m
> +CONFIG_NET_IPGRE_DEMUX=m
> +CONFIG_NF_CONNTRACK=m
> +CONFIG_NF_CONNTRACK_OVS=y
> +CONFIG_OPENVSWITCH=m
> +CONFIG_OPENVSWITCH_GENEVE=m
> +CONFIG_OPENVSWITCH_GRE=m
> +CONFIG_OPENVSWITCH_VXLAN=m
> +CONFIG_PSAMPLE=m
> +CONFIG_VETH=y
> +CONFIG_VLAN_8021Q=y
> +CONFIG_VXLAN=m


  parent reply	other threads:[~2026-07-16 15:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10 18:04 [PATCH net 0/7] selftests: net: add missing kconfig and settings Matthieu Baerts (NGI0)
2026-07-10 18:04 ` [PATCH net 1/7] selftests: af_unix: add USER_NS config Matthieu Baerts (NGI0)
2026-07-10 18:51   ` Kuniyuki Iwashima
2026-07-10 18:04 ` [PATCH net 2/7] selftests: openvswitch: add config file Matthieu Baerts (NGI0)
2026-07-16  8:15   ` Eelco Chaudron
2026-07-16 15:38   ` Aaron Conole [this message]
2026-07-16 20:00     ` Aaron Conole
2026-07-10 18:04 ` [PATCH net 3/7] selftests: ovpn: add IPV6 and VETH configs Matthieu Baerts (NGI0)
2026-07-13 11:42   ` Antonio Quartulli
2026-07-10 18:04 ` [PATCH net 4/7] selftests: ovpn: increase timeout Matthieu Baerts (NGI0)
2026-07-13 11:44   ` Antonio Quartulli
2026-07-10 18:04 ` [PATCH net 5/7] selftests: drv-net: " Matthieu Baerts (NGI0)
2026-07-10 18:04 ` [PATCH net 6/7] selftests: drv-net: add missing kconfig for psp.py Matthieu Baerts (NGI0)
2026-07-10 21:26   ` Wei Wang
2026-07-10 18:04 ` [PATCH net 7/7] selftests: netconsole: ignore busywait errors Matthieu Baerts (NGI0)
2026-07-13 10:41   ` Breno Leitao

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=f7t5x2frlkh.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=echaudro@redhat.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=i.maximets@ovn.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=matttbe@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