Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 30 Jun 2021 12:05:42 -0400
From:   Bruce Fields <bfields@fieldses.org>
To:     Chuck Lever III <chuck.lever@oracle.com>
Cc:     "Russell King (Oracle)" <linux@armlinux.org.uk>,
        Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: 5.13 NFSD: completely broken?
Message-ID: <20210630160542.GD20229@fieldses.org>
References: <20210630155325.GD22278@shell.armlinux.org.uk>
 <1BF34FA4-EC1A-405D-AA8B-217BF94DA219@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1BF34FA4-EC1A-405D-AA8B-217BF94DA219@oracle.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk

On Wed, Jun 30, 2021 at 03:55:16PM +0000, Chuck Lever III wrote:
> > On Jun 30, 2021, at 11:53 AM, Russell King (Oracle) <linux@armlinux.org.uk> wrote:
> > Has 5.13 been tested with nfsv3 ?
> > 
> > Any ideas what's going on?
> 
> Yes, fortunately!
> 
> Have a look at commit 66d9282523b for a one-liner fix, it should apply
> cleanly to v5.13.

So was this a freak event or do we need some process change?

Looks like the problem commit went in 3 days before 5.13.  It was an mm
commit so they're probably not set up to do nfsd testing, but nfsd is
the only user of that function, right?

It says it fixed a bug that could result in writing past the end of an
array, so made sense that it was urgent.

Sorry, just catching up!

--b.