From: Christian Schoenebeck <linux_oss@crudebyte.com>
To: ericvh@kernel.org, lucho@ionkov.net, asmadeus@codewreck.org,
Pierre Barre <pierre@barre.sh>
Cc: v9fs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 9p: fix data corruption with writeback caching during concurrent stat
Date: Sat, 27 Dec 2025 12:30:20 +0100 [thread overview]
Message-ID: <2393940.ElGaqSPkdT@weasel> (raw)
In-Reply-To: <20251227083751.715152-1-pierre@barre.sh>
On Saturday, 27 December 2025 09:37:51 CET Pierre Barre wrote:
> When using writeback caching (cache=mmap), v9fs_vfs_getattr/setattr have
> two issues that can cause data corruption:
>
> 1. filemap_fdatawrite() initiates writeback but doesn't wait for
> completion. The subsequent server stat sees stale file size.
>
> 2. v9fs_stat2inode()/v9fs_stat2inode_dotl() unconditionally overwrite
> i_size from the server response, even when dirty pages exist locally.
> This causes processes using lseek(SEEK_END) to see incorrect file
> sizes.
>
> Fix by using filemap_write_and_wait() instead of filemap_fdatawrite(),
> and passing V9FS_STAT2INODE_KEEP_ISIZE when CACHE_WRITEBACK is enabled
> to preserve the local i_size.
>
> Also fix v9fs_vfs_getattr_dotl() to check for CACHE_WRITEBACK specifically
> rather than any cache mode.
>
> Signed-off-by: Pierre Barre <pierre@barre.sh>
> ---
> fs/9p/vfs_inode.c | 11 ++++++++---
> fs/9p/vfs_inode_dotl.c | 13 +++++++++----
> 2 files changed, 17 insertions(+), 7 deletions(-)
>
> diff --git a/fs/9p/vfs_inode.c b/fs/9p/vfs_inode.c
> index 97abe65bf7c1..f4c294ca759b 100644
> --- a/fs/9p/vfs_inode.c
> +++ b/fs/9p/vfs_inode.c
> @@ -977,7 +977,7 @@ v9fs_vfs_getattr(struct mnt_idmap *idmap, const struct
> path *path, return 0;
> } else if (v9ses->cache & CACHE_WRITEBACK) {
> if (S_ISREG(inode->i_mode)) {
> - int retval = filemap_fdatawrite(inode->i_mapping);
> + int retval = filemap_write_and_wait(inode->i_mapping);
Haven't reviewed thorougly, but this looks wrong to me. The point about write-
back is not having to wait for completion.
> if (retval)
> p9_debug(P9_DEBUG_ERROR,
> @@ -993,7 +993,12 @@ v9fs_vfs_getattr(struct mnt_idmap *idmap, const struct
> path *path, if (IS_ERR(st))
> return PTR_ERR(st);
>
> - v9fs_stat2inode(st, d_inode(dentry), dentry->d_sb, 0);
> + /*
> + * With writeback caching, the client is authoritative for i_size.
> + * Don't let the server overwrite it with a potentially stale value.
> + */
> + v9fs_stat2inode(st, d_inode(dentry), dentry->d_sb,
> + (v9ses->cache & CACHE_WRITEBACK) ? V9FS_STAT2INODE_KEEP_ISIZE : 0);
And this measure alone (along with the same change in v9fs_vfs_getattr_dotl()
that is) would not fix the misbehavior you encountered?
> generic_fillattr(&nop_mnt_idmap, request_mask, d_inode(dentry), stat);
>
> p9stat_free(st);
> @@ -1058,7 +1063,7 @@ static int v9fs_vfs_setattr(struct mnt_idmap *idmap,
>
> /* Write all dirty data */
> if (d_is_reg(dentry)) {
> - retval = filemap_fdatawrite(inode->i_mapping);
> + retval = filemap_write_and_wait(inode->i_mapping);
> if (retval)
> p9_debug(P9_DEBUG_ERROR,
> "flushing writeback during setattr returned %d\n", retval);
> diff --git a/fs/9p/vfs_inode_dotl.c b/fs/9p/vfs_inode_dotl.c
> index 643e759eacb2..362a68a2bca3 100644
> --- a/fs/9p/vfs_inode_dotl.c
> +++ b/fs/9p/vfs_inode_dotl.c
> @@ -431,9 +431,9 @@ v9fs_vfs_getattr_dotl(struct mnt_idmap *idmap,
> if (v9ses->cache & (CACHE_META|CACHE_LOOSE)) {
> generic_fillattr(&nop_mnt_idmap, request_mask, inode, stat);
> return 0;
> - } else if (v9ses->cache) {
> + } else if (v9ses->cache & CACHE_WRITEBACK) {
OK, so here is an inconsistency between v9fs_vfs_getattr_dotl() and
v9fs_vfs_getattr(). But to me it should be the other way around, i.e.
v9fs_vfs_getattr() should do it any cache mode, not only for write-back?
/Christian
> if (S_ISREG(inode->i_mode)) {
> - int retval = filemap_fdatawrite(inode->i_mapping);
> + int retval = filemap_write_and_wait(inode->i_mapping);
>
> if (retval)
> p9_debug(P9_DEBUG_ERROR,
> @@ -453,7 +453,12 @@ v9fs_vfs_getattr_dotl(struct mnt_idmap *idmap,
> if (IS_ERR(st))
> return PTR_ERR(st);
>
> - v9fs_stat2inode_dotl(st, d_inode(dentry), 0);
> + /*
> + * With writeback caching, the client is authoritative for i_size.
> + * Don't let the server overwrite it with a potentially stale value.
> + */
> + v9fs_stat2inode_dotl(st, d_inode(dentry),
> + (v9ses->cache & CACHE_WRITEBACK) ? V9FS_STAT2INODE_KEEP_ISIZE : 0);
> generic_fillattr(&nop_mnt_idmap, request_mask, d_inode(dentry), stat);
> /* Change block size to what the server returned */
> stat->blksize = st->st_blksize;
> @@ -561,7 +566,7 @@ int v9fs_vfs_setattr_dotl(struct mnt_idmap *idmap,
>
> /* Write all dirty data */
> if (S_ISREG(inode->i_mode)) {
> - retval = filemap_fdatawrite(inode->i_mapping);
> + retval = filemap_write_and_wait(inode->i_mapping);
> if (retval < 0)
> p9_debug(P9_DEBUG_ERROR,
> "Flushing file prior to setattr failed: %d\n", retval);
next prev parent reply other threads:[~2025-12-27 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-27 8:37 [PATCH] 9p: fix data corruption with writeback caching during concurrent stat Pierre Barre
2025-12-27 11:30 ` Christian Schoenebeck [this message]
2025-12-27 17:58 ` Pierre Barre
2026-02-18 14:04 ` David Howells
2026-02-18 16:31 ` David Howells
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=2393940.ElGaqSPkdT@weasel \
--to=linux_oss@crudebyte.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=pierre@barre.sh \
--cc=v9fs@lists.linux.dev \
/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