From: Chuck Lever <chuck.lever@oracle.com>
To: Sergey Bashirov <sergeybashirov@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Konstantin Evtushenko <koevtushenko@yandex.com>
Subject: Re: [PATCH 2/2] NFSD: Fix last write offset handling in layoutcommit
Date: Fri, 4 Jul 2025 12:29:58 -0400 [thread overview]
Message-ID: <f1fdddde-2450-4a2c-a1e8-ee6a3ff81090@oracle.com> (raw)
In-Reply-To: <20250704114917.18551-3-sergeybashirov@gmail.com>
Hi Sergey, Konstantin -
On 7/4/25 7:49 AM, Sergey Bashirov wrote:
> The data type of loca_last_write_offset is newoffset4 and is switched
> on a boolean value, no_newoffset, that indicates if a previous write
> occurred or not. If no_newoffset is FALSE, an offset is not given.
> This means that client does not try to update the file size. Thus,
> server should not try to calculate new file size and check if it fits
> into the seg range.
The patch description should describe the impact of the current
incorrect logic -- does it result in file corruption, failed tests, etc?
That way support engineers at distributions can more easily find this
patch if a customer runs across bad behavior.
Also, let's reference RFC 8881 Section 12.5.4.2, where the properly
compliant behavior is specified.
Fixes: 9cf514ccfacb ("nfsd: implement pNFS operations")
> Co-developed-by: Konstantin Evtushenko <koevtushenko@yandex.com>
> Signed-off-by: Konstantin Evtushenko <koevtushenko@yandex.com>
> Signed-off-by: Sergey Bashirov <sergeybashirov@gmail.com>
> ---
> fs/nfsd/blocklayout.c | 2 +-
> fs/nfsd/nfs4proc.c | 16 ++++++++--------
> 2 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/fs/nfsd/blocklayout.c b/fs/nfsd/blocklayout.c
> index 19078a043e85..ee6544bdc045 100644
> --- a/fs/nfsd/blocklayout.c
> +++ b/fs/nfsd/blocklayout.c
> @@ -118,7 +118,7 @@ nfsd4_block_commit_blocks(struct inode *inode, struct nfsd4_layoutcommit *lcp,
> struct iomap *iomaps, int nr_iomaps)
> {
> struct timespec64 mtime = inode_get_mtime(inode);
> - loff_t new_size = lcp->lc_last_wr + 1;
> + loff_t new_size = (lcp->lc_newoffset) ? lcp->lc_last_wr + 1 : 0;
> struct iattr iattr = { .ia_valid = 0 };
> int error;
See below for an alternative.
> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
> index 37bdb937a0ae..ff38be803d8b 100644
> --- a/fs/nfsd/nfs4proc.c
> +++ b/fs/nfsd/nfs4proc.c
> @@ -2482,7 +2482,7 @@ nfsd4_layoutcommit(struct svc_rqst *rqstp,
> const struct nfsd4_layout_seg *seg = &lcp->lc_seg;
> struct svc_fh *current_fh = &cstate->current_fh;
> const struct nfsd4_layout_ops *ops;
> - loff_t new_size = lcp->lc_last_wr + 1;
> + loff_t new_size = (lcp->lc_newoffset) ? lcp->lc_last_wr + 1 : 0;
> struct inode *inode;
> struct nfs4_layout_stateid *ls;
> __be32 nfserr;
> @@ -2498,13 +2498,13 @@ nfsd4_layoutcommit(struct svc_rqst *rqstp,
> goto out;
> inode = d_inode(current_fh->fh_dentry);
>
How about instead, drop the new_size initializer above, and do this:
lcp->lc_size_chg = false;
if (lcp->lc_newoffset) {
loff_t new_size = lcp->lc_last_wr + 1;
nfserr = nfserr_inval;
if (new_size <= seg->offset)
goto out;
if (new_size > seg->offset + seg->length)
goto out;
if (new_size > i_size_read(inode)) {
lcp->lc_size_chg = true;
lcp->lc_newsize = new_size;
}
}
> - nfserr = nfserr_inval;
> - if (new_size <= seg->offset)
> - goto out;
> - if (new_size > seg->offset + seg->length)
> - goto out;
> - if (!lcp->lc_newoffset && new_size > i_size_read(inode))
> - goto out;
> + if (new_size) {
> + nfserr = nfserr_inval;
> + if (new_size <= seg->offset)
> + goto out;
> + if (new_size > seg->offset + seg->length)
> + goto out;
> + }
>
> nfserr = nfsd4_preprocess_layout_stateid(rqstp, cstate, &lcp->lc_sid,
> false, lcp->lc_layout_type,
And lastly:
- if (new_size > i_size_read(inode)) {
- lcp->lc_size_chg = true;
- lcp->lc_newsize = new_size;
- } else {
- lcp->lc_size_chg = false;
- }
Also, I notice that nfsd4_decode_layoutcommit() has:
if (xdr_stream_decode_bool(argp->xdr, &lcp->lc_reclaim) < 0)
return nfserr_bad_xdr;
but:
if (xdr_stream_decode_u32(argp->xdr, &lcp->lc_newoffset) < 0)
return nfserr_bad_xdr;
The no_newoffset field should be decoded with xdr_stream_decode_bool too
(though the end result is the same). For just this nit, please make a
separate patch. Thanks!
--
Chuck Lever
next prev parent reply other threads:[~2025-07-04 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 11:49 [PATCH 0/2] NFSD: Fix last write offset handling in layoutcommit Sergey Bashirov
2025-07-04 11:49 ` [PATCH 1/2] NFSD: Minor cleanup in layoutcommit processing Sergey Bashirov
2025-07-10 7:29 ` Christoph Hellwig
2025-07-04 11:49 ` [PATCH 2/2] NFSD: Fix last write offset handling in layoutcommit Sergey Bashirov
2025-07-04 16:29 ` Chuck Lever [this message]
2025-07-05 6:16 ` Sergey Bashirov
2025-07-06 15:01 ` Chuck Lever
2025-07-10 7:27 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2025-07-21 18:40 [PATCH 0/2] NFSD: Rebase dropped patches for block/scsi layout Sergey Bashirov
2025-07-21 18:40 ` [PATCH 2/2] NFSD: Fix last write offset handling in layoutcommit Sergey Bashirov
2025-07-21 18:56 ` Jeff Layton
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=f1fdddde-2450-4a2c-a1e8-ee6a3ff81090@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Dai.Ngo@oracle.com \
--cc=hch@infradead.org \
--cc=jlayton@kernel.org \
--cc=koevtushenko@yandex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=sergeybashirov@gmail.com \
--cc=tom@talpey.com \
/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