Re: [PATCH v2] fuse: keep inode->i_blkbits constant

[Christian Brauner <brauner@kernel.org>]

On Thu, 07 Aug 2025 10:50:15 -0700, Joanne Koong wrote:
> With fuse now using iomap for writeback handling, inode blkbits changes
> are problematic because iomap relies on inode->i_blkbits for its
> internal bitmap logic. Currently we change inode->i_blkbits in fuse to
> match the attr->blksize value passed in by the server.
> 
> This commit keeps inode->i_blkbits constant in fuse. Any attr->blksize
> values passed in by the server will not update inode->i_blkbits. The
> client-side behavior for stat is unaffected, stat will still reflect the
> blocksize passed in by the server.
> 
> [...]

Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes

[1/1] fuse: keep inode->i_blkbits constant
      https://git.kernel.org/vfs/vfs/c/0110b6d5545d