Re: [PATCH][RFC] iomap: add a private argument for iomap_file_buffered_write

[Christian Brauner <brauner@kernel.org>]

On Tue, 27 Aug 2024 06:51:36 -0400, Josef Bacik wrote:
> In order to switch fuse over to using iomap for buffered writes we need
> to be able to have the struct file for the original write, in case we
> have to read in the page to make it uptodate.  Handle this by using the
> existing private field in the iomap_iter, and add the argument to
> iomap_file_buffered_write.  This will allow us to pass the file in
> through the iomap buffered write path, and is flexible for any other
> file systems needs.
> 
> [...]

It's in vfs.blocksize because there's other work that touches iomap in there.
But I'll likely rename the branch to something that's more generic such as
vfs.iomap at some point soon now that we have other stuff coming in.

---

Applied to the vfs.blocksize branch of the vfs/vfs.git tree.
Patches in the vfs.blocksize 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.blocksize

[1/1] iomap: add a private argument for iomap_file_buffered_write
      https://git.kernel.org/vfs/vfs/c/f143d1a48d6e