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;
Date:   Fri, 28 Oct 2022 10:41:46 -0400
To:     Chuck Lever III <chuck.lever@oracle.com>
Cc:     Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Fwd: NFS 4 GPF while processing compound with multiple reads
Message-ID: <20221028144146.GA25371@fieldses.org>
References: <CAD15GZfmZYKmGs7GfaUwM1V65uLirgwYBwrvBj7VrUpmFUjOTQ@mail.gmail.com>
 <54463F56-C3EE-431B-9BEE-8B805AD011B9@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54463F56-C3EE-431B-9BEE-8B805AD011B9@oracle.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
From:   bfields@fieldses.org (J. Bruce Fields)
Precedence: bulk

On Thu, Oct 27, 2022 at 07:12:07PM +0000, Chuck Lever III wrote:
> 
> 
> > Begin forwarded message:
> > 
> > From: Jan Kasiak <j.kasiak@gmail.com>
> > Subject: NFS 4 GPF while processing compound with multiple reads
> > Date: October 27, 2022 at 2:16:36 PM EDT
> > To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
> > 
> > Hi all,
> > 
> > While writing my own NFS client, I have found a simple test case that
> > triggers a general protection fault on the NFS server.
> > 
> > The NFS 4 compound is: PUT_FH, READ, READ
> > The second read causes the fault.
> > 
> > More information, including how to reproduce the bug is available in
> > the bug tracker: https://bugzilla.linux-nfs.org/show_bug.cgi?id=402
> 
> Bruce, are you interested in applying:
> 
> https://bugzilla.linux-nfs.org/show_bug.cgi?id=402#c2

Applied and pushed out.  (But not actually tested!  Let me know if
there's a problem.)

--b.