From: "Darrick J. Wong" <djwong@kernel.org>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: brauner@kernel.org, miklos@szeredi.hu,
linux-fsdevel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2 2/2] fuse: fix fuseblk i_blkbits for iomap partial writes
Date: Thu, 14 Aug 2025 11:25:06 -0700 [thread overview]
Message-ID: <20250814182506.GY7942@frogsfrogsfrogs> (raw)
In-Reply-To: <20250813223521.734817-3-joannelkoong@gmail.com>
On Wed, Aug 13, 2025 at 03:35:21PM -0700, Joanne Koong wrote:
> On regular fuse filesystems, i_blkbits is set to PAGE_SHIFT which means
> any iomap partial writes will mark the entire folio as uptodate. However
> fuseblk filesystems work differently and allow the blocksize to be less
> than the page size. As such, this may lead to data corruption if fuseblk
> sets its blocksize to less than the page size, uses the writeback cache,
> and does a partial write, then a read and the read happens before the
> write has undergone writeback, since the folio will not be marked
> uptodate from the partial write so the read will read in the entire
> folio from disk, which will overwrite the partial write.
>
> The long-term solution for this, which will also be needed for fuse to
> enable large folios with the writeback cache on, is to have fuse also
> use iomap for folio reads, but until that is done, the cleanest
> workaround is to use the page size for fuseblk's internal kernel inode
> blksize/blkbits values while maintaining current behavior for stat().
>
> This was verified using ntfs-3g:
> $ sudo mkfs.ntfs -f -c 512 /dev/vdd1
> $ sudo ntfs-3g /dev/vdd1 ~/fuseblk
> $ stat ~/fuseblk/hi.txt
> IO Block: 512
>
> Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
> Fixes: a4c9ab1d4975 ("fuse: use iomap for buffered writes")
> ---
> fs/fuse/dir.c | 2 +-
> fs/fuse/fuse_i.h | 8 ++++++++
> fs/fuse/inode.c | 13 ++++++++++++-
> 3 files changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c
> index ebee7e0b1cd3..5c569c3cb53f 100644
> --- a/fs/fuse/dir.c
> +++ b/fs/fuse/dir.c
> @@ -1199,7 +1199,7 @@ static void fuse_fillattr(struct mnt_idmap *idmap, struct inode *inode,
> if (attr->blksize != 0)
> blkbits = ilog2(attr->blksize);
> else
> - blkbits = inode->i_sb->s_blocksize_bits;
> + blkbits = fc->blkbits;
>
> stat->blksize = 1 << blkbits;
> }
> diff --git a/fs/fuse/fuse_i.h b/fs/fuse/fuse_i.h
> index db44d05c8d02..a6aa16422c30 100644
> --- a/fs/fuse/fuse_i.h
> +++ b/fs/fuse/fuse_i.h
> @@ -975,6 +975,14 @@ struct fuse_conn {
> /* Request timeout (in jiffies). 0 = no timeout */
> unsigned int req_timeout;
> } timeout;
> +
> + /*
> + * This is a workaround until fuse uses iomap for reads.
> + * For fuseblk servers, this represents the blocksize passed in at
> + * mount time and for regular fuse servers, this is equivalent to
> + * inode->i_blkbits.
> + */
> + unsigned char blkbits;
uint8_t, since the value is an integer quantity, not a character.
> };
>
> /*
> diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
> index 3bfd83469d9f..7ddfd2b3cc9c 100644
> --- a/fs/fuse/inode.c
> +++ b/fs/fuse/inode.c
> @@ -292,7 +292,7 @@ void fuse_change_attributes_common(struct inode *inode, struct fuse_attr *attr,
> if (attr->blksize)
> fi->cached_i_blkbits = ilog2(attr->blksize);
> else
> - fi->cached_i_blkbits = inode->i_sb->s_blocksize_bits;
> + fi->cached_i_blkbits = fc->blkbits;
>
> /*
> * Don't set the sticky bit in i_mode, unless we want the VFS
> @@ -1810,10 +1810,21 @@ int fuse_fill_super_common(struct super_block *sb, struct fuse_fs_context *ctx)
> err = -EINVAL;
> if (!sb_set_blocksize(sb, ctx->blksize))
> goto err;
> + /*
> + * This is a workaround until fuse hooks into iomap for reads.
> + * Use PAGE_SIZE for the blocksize else if the writeback cache
> + * is enabled, buffered writes go through iomap and a read may
> + * overwrite partially written data if blocksize < PAGE_SIZE
> + */
> + fc->blkbits = sb->s_blocksize_bits;
> + if (ctx->blksize != PAGE_SIZE &&
> + !sb_set_blocksize(sb, PAGE_SIZE))
> + goto err;
> #endif
> } else {
> sb->s_blocksize = PAGE_SIZE;
> sb->s_blocksize_bits = PAGE_SHIFT;
> + fc->blkbits = sb->s_blocksize_bits;
> }
Heh. :)
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
(How long until readahead? ;))
--D
> sb->s_subtype = ctx->subtype;
> --
> 2.47.3
>
>
next prev parent reply other threads:[~2025-08-14 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 22:35 [PATCH v2 0/2] fuse: inode blocksize fixes for iomap integration Joanne Koong
2025-08-13 22:35 ` [PATCH v2 1/2] fuse: reflect cached blocksize if blocksize was changed Joanne Koong
2025-08-14 18:21 ` Darrick J. Wong
2025-08-13 22:35 ` [PATCH v2 2/2] fuse: fix fuseblk i_blkbits for iomap partial writes Joanne Koong
2025-08-14 18:25 ` Darrick J. Wong [this message]
2025-08-15 18:01 ` Joanne Koong
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=20250814182506.GY7942@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=joannelkoong@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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