Date:   Thu, 6 Jan 2022 13:34:31 -0500
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
Message-ID: <20220106183431.GE7969@fieldses.org>
References: <164010014140.6448.18108343631467243001.stgit@klimt.1015granger.net>
 <20220103210013.GK21514@fieldses.org>
 <BAA88CD4-C692-4AEE-9A8D-F62F8CBEA2F5@oracle.com>
 <20220104030708.GC27642@fieldses.org>
 <058a01d8032b$2992e740$7cb8b5c0$@mindspring.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <058a01d8032b$2992e740$7cb8b5c0$@mindspring.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk

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.