Re: [PATCH v3 23/35] xfs: add helper to check that inode data need fsverity verification

[Christoph Hellwig <hch@lst.de>]

On Wed, Feb 18, 2026 at 12:19:23AM +0100, Andrey Albershteyn wrote:
> +	       (offset < fsverity_metadata_offset(inode));

No need for the braces.

> +}
> +
> diff --git a/fs/xfs/xfs_fsverity.h b/fs/xfs/xfs_fsverity.h
> new file mode 100644
> index 000000000000..5fc55f42b317
> --- /dev/null
> +++ b/fs/xfs/xfs_fsverity.h
> @@ -0,0 +1,22 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +/*
> + * Copyright (C) 2026 Red Hat, Inc.
> + */
> +#ifndef __XFS_FSVERITY_H__
> +#define __XFS_FSVERITY_H__
> +
> +#include "xfs.h"
> +
> +#ifdef CONFIG_FS_VERITY
> +bool xfs_fsverity_sealed_data(const struct xfs_inode *ip,
> +		loff_t offset);
> +#else
> +static inline loff_t xfs_fsverity_offset_to_disk(struct xfs_inode *ip,
> +						 loff_t pos)
> +{
> +	WARN_ON_ONCE(1);
> +	return ULLONG_MAX;
> +}
> +#endif	/* CONFIG_FS_VERITY */

It looks like this got messed up a bit when splitting the patches and
you want an xfs_fsverity_sealed_data stub here?

Also I'm not sure introducing the "sealed" terminology just for this
function make much sense.  Just say xfs_is_fsverity_data maybe?