linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 'Bruce Fields' <bfields@fieldses.org>
To: Frank Filz <ffilzlnx@mindspring.com>
Cc: 'Chuck Lever III' <chuck.lever@oracle.com>,
	'Linux NFS Mailing List' <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH RFC] NFSD: Fix zero-length NFSv3 WRITEs
Date: Thu, 6 Jan 2022 13:34:31 -0500	[thread overview]
Message-ID: <20220106183431.GE7969@fieldses.org> (raw)
In-Reply-To: <058a01d8032b$2992e740$7cb8b5c0$@mindspring.com>

On Thu, Jan 06, 2022 at 10:28:10AM -0800, Frank Filz wrote:
> > On Tue, Jan 04, 2022 at 01:12:40AM +0000, Chuck Lever III wrote:
> > > > but still may be worth posting
> > > > somewhere and making it the start of a collection of protocol-level
> > > > v3 tests.
> > >
> > > ... I question whether it's worth posting anything until there is a
> > > framework for collecting and maintaining such things. I do agree that
> > > the community should be working up a set of NFSv3 specific tests like
> > > this. I like Frank's idea of making them a part of pynfs, fwiw.
> > 
> > Somebody did actually do a v3 pynfs that I never got around to merging,
> it'd be
> > worth revisiting:
> > 
> > 	https://github.com/sthaber/pynfs
> 
> I'm working on that... It requires significant effort, but I have made some
> progress:
> 
> https://github.com/ffilz/pynfs/commit/d3a1610815117cb6bdf6567e575baedb0d8809
> 5e
> 
> I need to get back to it, but it's lower on my priority list.

Oh, good to know, thanks.

--b.

  reply	other threads:[~2022-01-06 18:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 15:23 [PATCH RFC] NFSD: Fix zero-length NFSv3 WRITEs Chuck Lever
2022-01-03 21:00 ` J. Bruce Fields
2022-01-04  1:12   ` Chuck Lever III
2022-01-04  3:07     ` Bruce Fields
2022-01-06 18:28       ` Frank Filz
2022-01-06 18:34         ` 'Bruce Fields' [this message]
2022-01-06 19:37           ` Frank Filz
2022-01-06 19:43             ` 'Bruce Fields'

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=20220106183431.GE7969@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=ffilzlnx@mindspring.com \
    --cc=linux-nfs@vger.kernel.org \
    /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).