Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <9ee56f62652c3d338aff809f70e7941dfc284bf9.camel@kernel.org>
Subject: xfstests results over NFS
From:   Jeff Layton <jlayton@kernel.org>
To:     Chuck Lever <chuck.lever@oracle.com>,
        Trond Myklebust <trondmy@gmail.com>,
        Anna Schumaker <anna@kernel.org>
Cc:     linux-nfs <linux-nfs@vger.kernel.org>, NeilBrown <neilb@suse.de>,
        "Kornievskaia, Olga" <Olga.Kornievskaia@netapp.com>,
        Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Date:   Thu, 17 Aug 2023 07:21:46 -0400
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Precedence: bulk

I finally got my kdevops (https://github.com/linux-kdevops/kdevops) test
rig working well enough to get some publishable results. To run fstests,
kdevops will spin up a server and (in this case) 2 clients to run
xfstests' auto group. One client mounts with default options, and the
other uses NFSv3.

I tested 3 kernels:

v6.4.0 (stock release)
6.5.0-rc6-g4853c74bd7ab (Linus' tree as of a couple of days ago)
6.5.0-rc6-next-20230816-gef66bf8aeb91 (linux-next as of yesterday morning)

Here are the results summary of all 3:

KERNEL:    6.4.0
CPUS:      8

nfs_v3: 727 tests, 12 failures, 569 skipped, 14863 seconds
  Failures: generic/053 generic/099 generic/105 generic/124=20
    generic/193 generic/258 generic/294 generic/318 generic/319=20
    generic/444 generic/528 generic/529=20
nfs_default: 727 tests, 18 failures, 452 skipped, 21899 seconds
  Failures: generic/053 generic/099 generic/105 generic/186=20
    generic/187 generic/193 generic/294 generic/318 generic/319=20
    generic/357 generic/444 generic/486 generic/513 generic/528=20
    generic/529 generic/578 generic/675 generic/688=20
Totals: 1454 tests, 1021 skipped, 30 failures, 0 errors, 35096s

KERNEL:    6.5.0-rc6-g4853c74bd7ab
CPUS:      8

nfs_v3: 727 tests, 9 failures, 570 skipped, 14775 seconds
  Failures: generic/053 generic/099 generic/105 generic/258=20
    generic/294 generic/318 generic/319 generic/444 generic/529=20
nfs_default: 727 tests, 16 failures, 453 skipped, 22326 seconds
  Failures: generic/053 generic/099 generic/105 generic/186=20
    generic/187 generic/294 generic/318 generic/319 generic/357=20
    generic/444 generic/486 generic/513 generic/529 generic/578=20
    generic/675 generic/688=20
Totals: 1454 tests, 1023 skipped, 25 failures, 0 errors, 35396s

KERNEL:    6.5.0-rc6-next-20230816-gef66bf8aeb91
CPUS:      8

nfs_v3: 727 tests, 9 failures, 570 skipped, 14657 seconds
  Failures: generic/053 generic/099 generic/105 generic/258=20
    generic/294 generic/318 generic/319 generic/444 generic/529=20
nfs_default: 727 tests, 18 failures, 453 skipped, 21757 seconds
  Failures: generic/053 generic/099 generic/105 generic/186=20
    generic/187 generic/294 generic/318 generic/319 generic/357=20
    generic/444 generic/486 generic/513 generic/529 generic/578=20
    generic/675 generic/683 generic/684 generic/688=20
Totals: 1454 tests, 1023 skipped, 27 failures, 0 errors, 34870s

With NFSv4.2, v6.4.0 has 2 extra failures that the current mainline
kernel doesn't:

    generic/193	(some sort of setattr problem)
    generic/528	(known problem with btime handling in client that has been =
fixed)

While I haven't investigated, I'm assuming the 193 bug is also something
that has been fixed in recent kernels. There are also 3 other NFSv3
tests that started passing since v6.4.0. I haven't looked into those.

With the linux-next kernel there are 2 new regressions:

    generic/683
    generic/684

Both of these look like problems with setuid/setgid stripping, and still
need to be investigated. I have more verbose result info on the test
failures if anyone is interested.

Cheers,
--=20
Jeff Layton <jlayton@kernel.org>