linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: "bfields@fieldses.org" <bfields@fieldses.org>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
	"ltp@lists.linux.it" <ltp@lists.linux.it>,
	"chuck.lever@oracle.com" <chuck.lever@oracle.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"alexey.kodanev@oracle.com" <alexey.kodanev@oracle.com>,
	"yangx.jy@cn.fujitsu.com" <yangx.jy@cn.fujitsu.com>
Subject: Re: [RFC PATCH 1/1] Remove nfsv4
Date: Mon, 20 Jul 2020 17:15:08 +0200	[thread overview]
Message-ID: <20200720151508.GA13786@dell5510> (raw)
In-Reply-To: <20200720143620.GD21201@dell5510>

Hi Bruce, Trond,

> > On Mon, Jul 20, 2020 at 01:32:09PM +0000, Trond Myklebust wrote:
> > > On Mon, 2020-07-20 at 11:14 +0200, Petr Vorel wrote:
> > > > Reasons to drop:
> > > > * outdated tests (from 2005)
> > > > * not used (NFS kernel maintainers use pynfs [1])
> > > > * written in Python (we support C and shell, see [2])

> > > > [1] http://git.linux-nfs.org/?p=bfields/pynfs.git;a=summary
> > > > [2] https://github.com/linux-test-project/ltp/issues/547


> > > Unlike pynfs, these tests run on a real NFS client, and were designed
> > > to test client implementations, as well as the servers.

> > > So if they get dropped from ltp, then we will have to figure out some
> > > other way of continuing to maintain them.

> > Just for fun, I grepped through old mail to see if I could find any
> > cases of these tests being used.  I found one, in which Chuck reports an
> > nfslock01 failure.  Looks like it did find a real bug, which we fixed:

> > 	https://lore.kernel.org/r/8DF85CB6-5FEB-4A25-9715-C9808F37A4B1@oracle.com
> > 	https://lore.kernel.org/r/20160807185024.11705.10864.stgit@klimt.1015granger.net

> Thanks for your explanation, this obviously justify these tests in LTP, unless
> you want to move it to git.linux-nfs.org and maintain on your own.
Actually, that fix 42691398be08 ("nfsd: Fix race between FREE_STATEID and LOCK")
from v4.8-rc2 reported by Alexey Kodanev (LTP network maintainer) was found by
nfslock01 test [1], which is integrated into other LTP NFS tests [2]. I'd
definitely keep these in LTP.

nfsv4 I proposed to remove as outdated and not being used are testing ACL [3]
and fcntl locking [4]. ACL tests use rsh and aren't integrated into LTP
framework (use their custom [5] runtest file thus I doubt anyone is using it).
fcntl locktests are at least integrated into LTP (use fcntl-locktests runtest
file[6], I forget to remove it in this patch).
Both tests are written in 2005. I don't want to push for removal, if you see any
use in it.

Kind regards,
Petr

[1] https://github.com/linux-test-project/ltp/tree/master/testcases/network/nfs/nfslock01/
[2] https://github.com/linux-test-project/ltp/blob/master/runtest/net.nfs
[3] https://github.com/linux-test-project/ltp/tree/master/testcases/network/nfsv4/acl
[4] https://github.com/linux-test-project/ltp/tree/master/testcases/network/nfsv4/locks
[5] https://github.com/linux-test-project/ltp/blob/master/testcases/network/nfsv4/acl/runtest
[6] https://github.com/linux-test-project/ltp/blob/master/runtest/fcntl-locktests

  reply	other threads:[~2020-07-20 15:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  9:14 [RFC PATCH 1/1] Remove nfsv4 Petr Vorel
2020-07-20 13:32 ` Trond Myklebust
2020-07-20 14:12   ` bfields
2020-07-20 14:36     ` Petr Vorel
2020-07-20 15:15       ` Petr Vorel [this message]
2020-07-20 17:01         ` bfields
2020-07-20 18:12           ` Petr Vorel
2020-07-20 15:17   ` Christoph Hellwig
2020-07-20 18:16     ` Petr Vorel
2020-07-21  9:31       ` Petr Vorel

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=20200720151508.GA13786@dell5510 \
    --to=pvorel@suse.cz \
    --cc=alexey.kodanev@oracle.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=trondmy@hammerspace.com \
    --cc=yangx.jy@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).