From: cel@kernel.org
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 1/2] fstests: Run the NFS/RDMA section with NFSv4.1
Date: Sun, 13 Oct 2024 11:30:52 -0400 [thread overview]
Message-ID: <20241013153053.1431805-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
Seeing some test hangs here that might be due to known bugs in
NFSv4.2. Force the NFS/RDMA test section to use NFSv4.1, not
the default NFS version (which on modern distros is NFSv4.2).
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
playbooks/roles/fstests/templates/nfs/nfs.config | 4 ++--
workflows/fstests/nfs/Kconfig | 4 ++++
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/playbooks/roles/fstests/templates/nfs/nfs.config b/playbooks/roles/fstests/templates/nfs/nfs.config
index 00911af6437a..3605e582b2d7 100644
--- a/playbooks/roles/fstests/templates/nfs/nfs.config
+++ b/playbooks/roles/fstests/templates/nfs/nfs.config
@@ -22,14 +22,14 @@ MOUNT_OPTIONS="-o vers=4.1"
# Test over RDMA
[nfs_rdma]
TEST_FS_MOUNT_OPTS="-o rdma"
-MOUNT_OPTIONS="-o rdma"
+MOUNT_OPTIONS="-o rdma,vers=4.1"
{% endif %}
{% if fstests_nfs_section_tls -%}
# Test NFS with RPC over TLS
[nfs_tls]
TEST_FS_MOUNT_OPTS="-o xprtsec=mtls"
-MOUNT_OPTIONS="-o xprtsec=mtls"
+MOUNT_OPTIONS="-o xprtsec=mtls,vers=4.1"
{% endif %}
{% if fstests_nfs_section_nfsd -%}
diff --git a/workflows/fstests/nfs/Kconfig b/workflows/fstests/nfs/Kconfig
index 0b32e710fa58..3c373d7eedfc 100644
--- a/workflows/fstests/nfs/Kconfig
+++ b/workflows/fstests/nfs/Kconfig
@@ -61,6 +61,8 @@ config FSTESTS_NFS_SECTION_RDMA
the target nodes have RDMA hardware already, enable one of
the software RDMA options as well.
+ This test uses an NFSv4.1 mount.
+
config FSTESTS_NFS_SECTION_TLS
bool "Enable testing section: nfs_tls"
default n
@@ -68,6 +70,8 @@ config FSTESTS_NFS_SECTION_TLS
help
Enabling this will test with the xprtsec=tls mount option.
+ This test uses an NFSv4.1 mount.
+
config FSTESTS_NFS_SECTION_NFSD
bool "Enable testing section: nfsd"
output yaml
--
2.46.1
next reply other threads:[~2024-10-13 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 15:30 cel [this message]
2024-10-13 15:30 ` [PATCH 2/2] gitr: Update default git version to be cloned cel
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=20241013153053.1431805-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
/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