From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Skorodumov <dskr99@gmail.com>
Cc: netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Dmitry Skorodumov <skorodumov.dmitry@huawei.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v4 net 2/2] selftests: net: simple selftest for ipvtap
Date: Fri, 2 Jan 2026 12:26:37 -0800 [thread overview]
Message-ID: <20260102122637.40556d72@kernel.org> (raw)
In-Reply-To: <20251230140333.2088391-3-skorodumov.dmitry@huawei.com>
On Tue, 30 Dec 2025 17:03:24 +0300 Dmitry Skorodumov wrote:
> @@ -122,6 +123,7 @@ CONFIG_TEST_BPF=m
> CONFIG_TLS=m
> CONFIG_TRACEPOINTS=y
> CONFIG_TUN=y
> +CONFIG_TAP=m
alphabetical order please
> CONFIG_USER_NS=y
> CONFIG_VETH=y
> CONFIG_VLAN_8021Q=y
> diff --git a/tools/testing/selftests/net/ipvtap_test.sh b/tools/testing/selftests/net/ipvtap_test.sh
> new file mode 100755
> +NS_COUNT=32
> +IP_ITERATIONS=1024
> +[ "$KSFT_MACHINE_SLOW" = "yes" ] && NS_COUNT=8
This still fails on our slow VMs with debug kernel enabled (even tho
they set KSFT_MACHINE_SLOW). The test runs for 15+ minutes without
printing anything. That's pretty bad, humans running this tests will
also have no idea what's going on. Maybe limit the runtime of the test
as well as the iterations? To 1min? It takes <50sec on non-debug kernels
in our CI.
--
pw-bot: cr
prev parent reply other threads:[~2026-01-02 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 14:03 [PATCH v4 net 0/2] ipvlan: addrs_lock made per port Dmitry Skorodumov
2025-12-30 14:03 ` [PATCH v4 net 1/2] ipvlan: Make the addrs_lock be " Dmitry Skorodumov
2025-12-30 14:03 ` [PATCH v4 net 2/2] selftests: net: simple selftest for ipvtap Dmitry Skorodumov
2026-01-02 20:26 ` Jakub Kicinski [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=20260102122637.40556d72@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dskr99@gmail.com \
--cc=edumazet@google.com \
--cc=horms@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=skorodumov.dmitry@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).