[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <174982965908.544557.2417180115604364588.b4-ty@oracle.com>
Date: Fri, 13 Jun 2025 11:48:38 -0400
From: Chuck Lever <cel@...nel.org>
To: Christoph Hellwig <hch@...radead.org>,
Jeff Layton <jlayton@...nel.org>,
NeilBrown <neil@...wn.name>,
Olga Kornievskaia <okorniev@...hat.com>,
Dai Ngo <Dai.Ngo@...cle.com>,
Tom Talpey <tom@...pey.com>,
Sergey Bashirov <sergeybashirov@...il.com>
Cc: Chuck Lever <chuck.lever@...cle.com>,
linux-nfs@...r.kernel.org,
linux-kernel@...r.kernel.org,
Konstantin Evtushenko <koevtushenko@...dex.com>
Subject: Re: [PATCH v3] nfsd: Use correct error code when decoding extents
From: Chuck Lever <chuck.lever@...cle.com>
On Fri, 13 Jun 2025 00:42:49 +0300, Sergey Bashirov wrote:
> Update error codes in decoding functions of block and scsi layout
> drivers to match the core nfsd code. NFS4ERR_EINVAL means that the
> server was able to decode the request, but the decoded values are
> invalid. Use NFS4ERR_BADXDR instead to indicate a decoding error.
> And ENOMEM is changed to nfs code NFS4ERR_DELAY.
>
>
> [...]
Applied to nfsd-testing, thanks!
[1/1] nfsd: Use correct error code when decoding extents
commit: 9558037b8e9d90f099f1c6387151ad3282c28b66
--
Chuck Lever
Powered by blists - more mailing lists