Re: [PATCH v3 12/35] iomap: let fsverity verify holes

["Darrick J. Wong" <djwong@kernel.org>]

On Wed, Feb 18, 2026 at 12:19:12AM +0100, Andrey Albershteyn wrote:
> fsverity needs to verify consistency of the files against the root hash,
> the holes are also hashed in the tree.
> 
> Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
> ---
>  fs/iomap/buffered-io.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
> index 6ebf68fdc386..9468c5d60b23 100644
> --- a/fs/iomap/buffered-io.c
> +++ b/fs/iomap/buffered-io.c
> @@ -553,6 +553,9 @@ static int iomap_read_folio_iter(struct iomap_iter *iter,
>  		if (iomap_block_needs_zeroing(iter, pos) &&
>  		    !(iomap->flags & IOMAP_F_FSVERITY)) {
>  			folio_zero_range(folio, poff, plen);
> +			if (fsverity_active(iter->inode) &&
> +			    !fsverity_verify_blocks(ctx->vi, folio, plen, poff))
> +				return -EIO;

Assuming that EIO really is the error code for "data doesn't match
merkle tree") then this is ok.  Too bad the function returns a bool
and makes the filesystems come up with their own error code... :(

--D

>  			iomap_set_range_uptodate(folio, poff, plen);
>  		} else {
>  			/*
> -- 
> 2.51.2
> 
>