From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/1] Remove nfsv4
Date: Mon, 20 Jul 2020 16:36:20 +0200 [thread overview]
Message-ID: <20200720143620.GD21201@dell5510> (raw)
In-Reply-To: <20200720141255.GA25707@fieldses.org>
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.
Kind regards,
Petr
next prev parent reply other threads:[~2020-07-20 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 9:14 [LTP] [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 [this message]
2020-07-20 15:15 ` Petr Vorel
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=20200720143620.GD21201@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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