From: Jeff Layton <jlayton@kernel.org>
To: Anna Schumaker <anna@kernel.org>,
Trond Myklebust <trondmy@hammerspace.com>,
Chuck Lever <chuck.lever@oracle.com>,
Yongcheng Yang <yoyang@redhat.com>,
linux-nfs@vger.kernel.org, fstests@vger.kernel.org,
Jeff Layton <jlayton@kernel.org>
Subject: [PATCH fstests 1/2] generic/465: don't run it on NFS
Date: Wed, 10 Jan 2024 13:27:27 -0500 [thread overview]
Message-ID: <20240110-fixes-v1-1-69f5ddd95656@kernel.org> (raw)
In-Reply-To: <20240110-fixes-v1-0-69f5ddd95656@kernel.org>
This test kicks off a thread that issues a read against a file, while
writing to the file in 1M chunks. It expects that the reader will see
either the written data or a short read.
NFS allows DIO reads and writes to run in parallel. That means that it's
possible for them to race and the reader to see NULLs in the file if
things get reordered.
Just skip this test on NFS, since we can't guarantee that it will
reliably pass.
Cc: Anna Schumaker <anna@kernel.org>
Cc: Trond Myklebust <trondmy@hammerspace.com>
Cc: Chuck Lever <chuck.lever@oracle.com>
Link: https://lore.kernel.org/linux-nfs/2f7f6d4490ac08013ef78481ff5c7840f41b1bb4.camel@kernel.org/
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
tests/generic/465 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/generic/465 b/tests/generic/465
index 73fdfb5548af..0745d6a1dd3a 100755
--- a/tests/generic/465
+++ b/tests/generic/465
@@ -21,7 +21,7 @@ _cleanup()
. ./common/filter
# real QA test starts here
-_supported_fs generic
+_supported_fs ^nfs
_require_aiodio aio-dio-append-write-read-race
_require_test_program "feature"
--
2.43.0
next prev parent reply other threads:[~2024-01-10 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 18:27 [PATCH fstests 0/2] generic: skip a couple more tests on NFS Jeff Layton
2024-01-10 18:27 ` Jeff Layton [this message]
2024-01-11 20:47 ` [PATCH fstests 1/2] generic/465: don't run it " Zorro Lang
2024-01-10 18:27 ` [PATCH fstests 2/2] generic/732: " Jeff Layton
2024-01-11 20:49 ` Zorro Lang
2024-01-11 21:13 ` Jeff Layton
2024-01-12 13:35 ` Zorro Lang
2024-01-12 13:36 ` Zorro Lang
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=20240110-fixes-v1-1-69f5ddd95656@kernel.org \
--to=jlayton@kernel.org \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.com \
--cc=yoyang@redhat.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