From: Joanne Koong <joannelkoong@gmail.com>
To: brauner@kernel.org
Cc: miklos@szeredi.hu, djwong@kernel.org,
linux-fsdevel@vger.kernel.org, kernel-team@meta.com
Subject: [PATCH v3 0/2] fuse: inode blocksize fixes for iomap integration
Date: Fri, 15 Aug 2025 11:25:37 -0700 [thread overview]
Message-ID: <20250815182539.556868-1-joannelkoong@gmail.com> (raw)
These 2 patches are fixes for inode blocksize usage in fuse.
The first is neededed to maintain current stat() behavior for clients in the
case where fuse uses cached values for stat, and the second is needed for
fuseblk filesystems as a workaround until fuse implements iomap for reads.
These patches are on top of Christian's vfs.fixes tree.
Thanks,
Joanne
Changelog
v2: https://lore.kernel.org/linux-fsdevel/20250813223521.734817-1-joannelkoong@gmail.com/
v2 -> v3:
- use u8 instead of unsigned char for blkbits type (Darrick)
v1: https://lore.kernel.org/linux-fsdevel/20250812214614.2674485-1-joannelkoong@gmail.com/
v1 -> v2:
- fix spacing to avoid overly long line
- add ctx->blksize check
Joanne Koong (2):
fuse: reflect cached blocksize if blocksize was changed
fuse: fix fuseblk i_blkbits for iomap partial writes
fs/fuse/dir.c | 3 ++-
fs/fuse/fuse_i.h | 14 ++++++++++++++
fs/fuse/inode.c | 16 ++++++++++++++++
3 files changed, 32 insertions(+), 1 deletion(-)
--
2.47.3
next reply other threads:[~2025-08-15 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 18:25 Joanne Koong [this message]
2025-08-15 18:25 ` [PATCH v3 1/2] fuse: reflect cached blocksize if blocksize was changed Joanne Koong
2025-08-18 8:32 ` Chunsheng Luo
2025-08-19 14:43 ` Miklos Szeredi
2025-08-20 2:38 ` Chunsheng Luo
2025-08-15 18:25 ` [PATCH v3 2/2] fuse: fix fuseblk i_blkbits for iomap partial writes Joanne Koong
2025-08-19 8:26 ` [PATCH v3 0/2] fuse: inode blocksize fixes for iomap integration Christian Brauner
2025-08-19 8:35 ` Miklos Szeredi
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=20250815182539.556868-1-joannelkoong@gmail.com \
--to=joannelkoong@gmail.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).