public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Aleksei Oladko <aleksey.oladko@virtuozzo.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Shuah Khan <shuah@kernel.org>, Aaron Conole <aconole@redhat.com>,
	Ilya Maximets <imaximet@redhat.com>,
	Eelco Chaudron <echaudro@redhat.com>,
	Stefano Brivio <sbrivio@redhat.com>,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, dev@openvswitch.org
Subject: Re: [PATCH net-next v5 0/4] selftests: net: fix false failures due to missing features and host interference
Date: Fri, 20 Mar 2026 16:25:15 +0000	[thread overview]
Message-ID: <20260320162515.GA74886@horms.kernel.org> (raw)
In-Reply-To: <20260319103123.146112-1-aleksey.oladko@virtuozzo.com>

On Thu, Mar 19, 2026 at 10:31:19AM +0000, Aleksei Oladko wrote:
> Hi,
> 
> This series addresses several issues in the networking kselftests
> that cause false-positive failures depending on the host environment,
> kernel configuration, or library versions.
> 
> The main focus of these changes is to isolate tests from the host
> environment (using namespaces) and to ensure proper fallback or
> skipping when dependencies are missing.
> 
> Summary of changes:
> 1. Fixes ovs-dpctl.py to return a non-zero exit code when pyroute2
>    is too old. This allows pmtu.sh to correctly fall back to ovs-vsctl
>    instead of assuming the configuration was successful.
> 2-4. Move reuseport test into dedicated network namespaces. This prevents
>    failures caused by port conflicts with host processes or interference
>    from host firewall rules.
> 5. Ensures io_uring is enabled via sysctl before running io_uring_zerocopy
>    test, preventing failures on systems where kernel.io_uring_disabled
>    is set.
> 
> Signed-off-by: Aleksei Oladko <aleksey.oladko@virtuozzo.com>

Hi,

Unfortunately this series does not apply cleanly to net-next,
which breaks out CI.

Please rebase and repost.

Thanks!

-- 
pw-bot: changes-requested

      parent reply	other threads:[~2026-03-20 16:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 10:31 [PATCH net-next v5 0/4] selftests: net: fix false failures due to missing features and host interference Aleksei Oladko
2026-03-19 10:31 ` [PATCH net-next v5 1/4] selftests: net: run reuseport in an isolated netns Aleksei Oladko
2026-03-19 10:31 ` [PATCH net-next v5 2/4] selftests: net: rename pmtu.sh to pmtu-test.sh Aleksei Oladko
2026-03-19 10:31 ` [PATCH net-next v5 3/4] selftests: net: run pmtu.sh in netns to avoid host firewall interference Aleksei Oladko
2026-03-19 10:31 ` [PATCH net-next v5 4/4] selftests: net: io_uring_zerocopy: enable io_uring for the test Aleksei Oladko
2026-03-20 16:25 ` Simon Horman [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=20260320162515.GA74886@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=aconole@redhat.com \
    --cc=aleksey.oladko@virtuozzo.com \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=echaudro@redhat.com \
    --cc=edumazet@google.com \
    --cc=imaximet@redhat.com \
    --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=sbrivio@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