From: Trond Myklebust <trondmy@kernel.org>
To: Dai Ngo <dai.ngo@oracle.com>, anna@kernel.org
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] Don't always trust server inode size while client holds write delegation
Date: Mon, 13 Apr 2026 15:19:51 -0700 [thread overview]
Message-ID: <42bbd9bd83e0887c469a555bc5c76ec06aee722c.camel@kernel.org> (raw)
In-Reply-To: <20260401185322.2691848-1-dai.ngo@oracle.com>
Hi Dai,
On Wed, 2026-04-01 at 11:52 -0700, Dai Ngo wrote:
> With a write delegation, the server permits the client to buffer
> writes
> and associated metadata updates (including file size changes) locally
> and
> defer propagating them to the server. As a result, the server-
> reported
> GETATTR size may legitimately lag behind the client’s cached size for
> the
> duration of the delegation, so it must not be treated as
> authoritative.
>
> This patch modifies nfs_wcc_update_inode to update the cached inode
> size
> only when the client does not hold a write delegation or the
> cache_validity
> of the nfs_inode has the NFS_INO_INVALID_SIZE bit set.
>
> Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
> ---
> fs/nfs/inode.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
> index 4786343eeee0..21161ebbd953 100644
> --- a/fs/nfs/inode.c
> +++ b/fs/nfs/inode.c
> @@ -1649,8 +1649,11 @@ static void nfs_wcc_update_inode(struct inode
> *inode, struct nfs_fattr *fattr)
> && (fattr->valid & NFS_ATTR_FATTR_SIZE)
> && i_size_read(inode) ==
> nfs_size_to_loff_t(fattr->pre_size)
> && !nfs_have_writebacks(inode)) {
> - trace_nfs_size_wcc(inode, fattr->size);
> - i_size_write(inode, nfs_size_to_loff_t(fattr-
> >size));
> + if ((!nfs_have_write_delegation(inode)) ||
> + (NFS_I(inode)->cache_validity &
> NFS_INO_INVALID_SIZE)) {
> + trace_nfs_size_wcc(inode, fattr->size);
> + i_size_write(inode,
> nfs_size_to_loff_t(fattr->size));
> + }
> }
> }
>
Under what circumstances are you seeing this making a difference?
Please see the call to nfs_writeback_check_extend() in
nfs_writeback_update_inode() which is supposed to prevent the issue
you're talking about.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trondmy@kernel.org, trond.myklebust@hammerspace.com
prev parent reply other threads:[~2026-04-13 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 18:52 [PATCH 1/1] Don't always trust server inode size while client holds write delegation Dai Ngo
2026-04-13 22:19 ` Trond Myklebust [this message]
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=42bbd9bd83e0887c469a555bc5c76ec06aee722c.camel@kernel.org \
--to=trondmy@kernel.org \
--cc=anna@kernel.org \
--cc=dai.ngo@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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