From 4fd042e0465c97ba84b244ca1018698f44bbf1db Mon Sep 17 00:00:00 2001 From: Jeff Layton Date: Wed, 10 Jan 2024 13:27:28 -0500 Subject: 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 Signed-off-by: Jeff Layton Reviewed-by: Zorro Lang Signed-off-by: Zorro Lang --- tests/generic/732 | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/tests/generic/732 b/tests/generic/732 index 785aac58..5b5087d5 100755 --- a/tests/generic/732 +++ b/tests/generic/732 @@ -22,9 +22,7 @@ _cleanup() } # real QA test starts here -_supported_fs generic -[ "$FSTYP" = "nfs" ] && _fixed_by_kernel_commit fdd2630a739819 \ - "nfsd: fix change_info in NFSv4 RENAME replies" +_supported_fs ^nfs _require_test _require_scratch -- cgit v1.2.3