From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Cc: Olga Kornievskaia <olga.kornievskaia@gmail.com>,
Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Chuck Lever <chuck.lever@oracle.com>,
Anna Schumaker <Anna.Schumaker@Netapp.com>
Subject: [LTP] [PATCH 1/1] runtest/net.nfs: Run nfs02_06 on TCP only
Date: Thu, 22 Jun 2023 10:46:48 +0200 [thread overview]
Message-ID: <20230622084648.490498-1-pvorel@suse.cz> (raw)
UDP support disabled was on NFS server in kernel 5.6.
Due that 2 of 3 nfs06.sh tests runs are being skipped on newer kernels.
Therefore NFSv3 job in nfs02_06 test as TCP. This way all jobs in the
test are TCP, thus test will not be skipped. This also bring NFSv3
testing also under TCP (previously it was tested only on UDP).
Keep UDP in nfs01_06 jobs, so that NFSv3 on UDP is still covered for
older kernels.
Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
runtest/net.nfs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/runtest/net.nfs b/runtest/net.nfs
index 72cf4b307..15a960017 100644
--- a/runtest/net.nfs
+++ b/runtest/net.nfs
@@ -58,7 +58,7 @@ nfs41_ipv6_05 nfs05.sh -6 -v 4.1 -t tcp
nfs42_ipv6_05 nfs05.sh -6 -v 4.2 -t tcp
nfs01_06 nfs06.sh -v "3,3,3,4,4,4" -t "udp,udp,tcp,tcp,tcp,tcp"
-nfs02_06 nfs06.sh -v "3,4,4.1,4.2,4.2,4.2" -t "udp,tcp,tcp,tcp,tcp,tcp"
+nfs02_06 nfs06.sh -v "3,4,4.1,4.2,4.2,4.2" -t "tcp,tcp,tcp,tcp,tcp,tcp"
nfs03_ipv6_06 nfs06.sh -6 -v "4,4.1,4.1,4.2,4.2,4.2" -t "tcp,tcp,tcp,tcp,tcp,tcp"
nfs3_07 nfs07.sh -v 3 -t udp
--
2.40.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2023-06-22 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 8:46 Petr Vorel [this message]
2023-07-12 7:51 ` [LTP] [PATCH 1/1] runtest/net.nfs: Run nfs02_06 on TCP only Cyril Hrubis
2023-07-12 8:37 ` Petr Vorel
2023-07-12 10:28 ` Jeff Layton
2023-07-12 11:18 ` Petr Vorel
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=20230622084648.490498-1-pvorel@suse.cz \
--to=pvorel@suse.cz \
--cc=Anna.Schumaker@Netapp.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=olga.kornievskaia@gmail.com \
--cc=trond.myklebust@hammerspace.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).