On Tue, May 03, 2022 at 11:36:45PM +0200, Andreas Gruenbacher wrote:
> The @lend parameter of truncate_pagecache_range() should be the offset
> of the last byte of the hole, not the first byte beyond it.
>
> Fixes: ae259a9c8593 ("fs: introduce iomap infrastructure")
Hm, yes, this is _true_, but it's a fix without importance (except maybe
for an overflow case?) Look at the condition this is called in. We
aren't punching out an extra byte in the page cache because we're
punching beyond the end of the file.
It should be fixed because people copy-and-paste code. But it's not
urgent, and doesn't need to be backported.
Reviewed-by: Matthew Wilcox (Oracle) <willy@xxxxxxxxxxxxx>
> Signed-off-by: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
> ---
> fs/iomap/buffered-io.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
> index 8ce8720093b9..358ee1fb6f0d 100644
> --- a/fs/iomap/buffered-io.c
> +++ b/fs/iomap/buffered-io.c
> @@ -531,7 +531,8 @@ iomap_write_failed(struct inode *inode, loff_t pos, unsigned len)
> * write started inside the existing inode size.
> */
> if (pos + len > i_size)
> - truncate_pagecache_range(inode, max(pos, i_size), pos + len);
> + truncate_pagecache_range(inode, max(pos, i_size),
> + pos + len - 1);
> }
>
> static int iomap_read_folio_sync(loff_t block_start, struct folio *folio,
> --
> 2.35.1
>
