]> www.infradead.org Git - users/hch/xfstests-dev.git/commit
generic/732: don't run it on NFS
authorJeff Layton <jlayton@kernel.org>
Wed, 10 Jan 2024 18:27:28 +0000 (13:27 -0500)
committerZorro Lang <zlang@kernel.org>
Sun, 14 Jan 2024 12:39:09 +0000 (20:39 +0800)
commit4fd042e0465c97ba84b244ca1018698f44bbf1db
tree4515f3f74000850924f2a96a15e78b23b5fddb2a
parent8729dc6d13cb52529afdb1ba0ce292bd0f0159a9
generic/732: don't run it on NFS

This test sets up two independent superblocks with the same backend
server, and then does RENAMES of the same files in the two servers. This
is basically trying to simulate the case where two clients are competing
to rename files in the same directory on the same server.

This test would usually pass vs. an NFSv4 server that doesn't have
dfdd2630a7398 ("nfsd: fix change_info in NFSv4 RENAME replies"), because
the client would end up improperly invalidating the dcache for the whole
dir after most RENAMEs.

However, this test doesn't (and shouldn't) pass on NFS, because the
client has no idea that a rename has happened on the second mount. The
expected behavior for the NFS client is for it to use the cache timeouts
in this case, which is what it now does with the above server bug fixed.

Exempt NFS from running this test, since we don't expect it to pass.

Cc: Yongcheng Yang <yoyang@redhat.com>
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: Zorro Lang <zlang@redhat.com>
Signed-off-by: Zorro Lang <zlang@kernel.org>
tests/generic/732