[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240625174149.3d37ed88@elisabeth>
Date: Tue, 25 Jun 2024 17:41:49 +0200
From: Stefano Brivio <sbrivio@...hat.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Aaron Conole <aconole@...hat.com>, Paolo Abeni <pabeni@...hat.com>,
netdev@...r.kernel.org, dev@...nvswitch.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org, Pravin B
Shelar <pshelar@....org>, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Shuah Khan <shuah@...nel.org>,
Adrián Moreno <amorenoz@...hat.com>, Simon Horman
<horms@...nel.org>, David Ahern <dsahern@...il.com>
Subject: Re: [PATCH v2 net-next 0/7] selftests: net: Switch pmtu.sh to use
the internal ovs script.
On Tue, 25 Jun 2024 07:06:54 -0700
Jakub Kicinski <kuba@...nel.org> wrote:
> On Tue, 25 Jun 2024 09:20:29 -0400 Aaron Conole wrote:
> > > I'm still wondering if the issue is Kconfig-related (plus possibly bad
> > > interaction with vng). I don't see the OVS knob enabled in the self-
> > > tests config. If it's implied by some other knob, and ends-up being
> > > selected as a module, vng could stumble upon loading the module at
> > > runtime, especially on incremental build (at least I experience that
> > > problem locally). I'm not even sure if the KCI is building
> > > incrementally or not, so all the above could is quite a wild guess.
> > >
> > > In any case I think adding the explicit CONFIG_OPENVSWITCH=y the
> > > selftest config would make the scenario more well defined.
> >
> > That is in 7/7 - but there was a collision with a netfilter knob getting
> > turned on. I can repost it as-is (just after rebasing) if you think
> > that is the only issue.
>
> Sorry for not checking it earlier, looks like the runner was missing
> pyroute:
>
> # python3 ./tools/testing/selftests/net/openvswitch/ovs-dpctl.py
> Need to install the python pyroute2 package >= 0.6.
>
> I guess run_cmd counter-productively eats the stderr output ? :(
Yes, otherwise it's rather noisy, but you can run the thing with
VERBOSE=1, see also 56490b623aa0 ("selftests: Add debugging options to
pmtu.sh").
Before that change, we didn't eat standard error, but in the general
case I guess it's quite an improvement.
--
Stefano
Powered by blists - more mailing lists