From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@redhat.com>
Cc: fsverity@lists.linux.dev, linux-xfs@vger.kernel.org,
ebiggers@kernel.org, linux-fsdevel@vger.kernel.org,
aalbersh@kernel.org, david@fromorbit.com, hch@lst.de
Subject: Re: [PATCH v2 5/22] iomap: integrate fs-verity verification into iomap's read path
Date: Mon, 12 Jan 2026 14:35:55 -0800 [thread overview]
Message-ID: <20260112223555.GL15551@frogsfrogsfrogs> (raw)
In-Reply-To: <fm6mhsjqpa4tgpubffqp6rdeinvjkp6ugdmpafzelydx6sxep2@vriwphnloylb>
On Mon, Jan 12, 2026 at 03:50:26PM +0100, Andrey Albershteyn wrote:
> This patch adds fs-verity verification into iomap's read path. After
> BIO's io operation is complete the data are verified against
> fs-verity's Merkle tree. Verification work is done in a separate
> workqueue.
>
> The read path ioend iomap_read_ioend are stored side by side with
> BIOs if FS_VERITY is enabled.
>
> Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
> ---
> fs/iomap/bio.c | 66 ++++++++++++++++++++++++++++++++++++++++++++++++----
> fs/iomap/buffered-io.c | 12 ++++++++-
> fs/iomap/ioend.c | 41 +++++++++++++++++++++++++++++++-
> include/linux/iomap.h | 11 ++++++++
> 4 files changed, 123 insertions(+), 7 deletions(-)
>
> diff --git a/fs/iomap/bio.c b/fs/iomap/bio.c
> index fc045f2e4c..ac6c16b1f8 100644
> --- a/fs/iomap/bio.c
> +++ b/fs/iomap/bio.c
> @@ -5,6 +5,7 @@
> */
> #include <linux/iomap.h>
> #include <linux/pagemap.h>
> +#include <linux/fsverity.h>
> #include "internal.h"
> #include "trace.h"
>
> @@ -18,6 +19,60 @@
> bio_put(bio);
> }
>
> +#ifdef CONFIG_FS_VERITY
Should all this stuff go into fs/iomap/fsverity.c instead of ifdef'd
around the iomap code?
<shrug>
> +static void
> +iomap_read_fsverify_end_io_work(struct work_struct *work)
> +{
> + struct iomap_fsverity_bio *fbio =
> + container_of(work, struct iomap_fsverity_bio, work);
> +
> + fsverity_verify_bio(&fbio->bio);
> + iomap_read_end_io(&fbio->bio);
> +}
> +
> +static void
> +iomap_read_fsverity_end_io(struct bio *bio)
> +{
> + struct iomap_fsverity_bio *fbio =
> + container_of(bio, struct iomap_fsverity_bio, bio);
> +
> + INIT_WORK(&fbio->work, iomap_read_fsverify_end_io_work);
> + fsverity_enqueue_verify_work(&fbio->work);
> +}
> +
> +static struct bio *
> +iomap_fsverity_read_bio_alloc(struct inode *inode, struct block_device *bdev,
> + int nr_vecs, gfp_t gfp)
> +{
> + struct bio *bio;
> +
> + bio = bio_alloc_bioset(bdev, nr_vecs, REQ_OP_READ, gfp,
> + iomap_fsverity_bioset);
> + if (bio)
> + bio->bi_end_io = iomap_read_fsverity_end_io;
> + return bio;
> +}
> +
> +#else
> +# define iomap_fsverity_read_bio_alloc(...) (NULL)
> +# define iomap_fsverity_tree_end_align(...) (false)
> +#endif /* CONFIG_FS_VERITY */
> +
> +static struct bio *iomap_read_bio_alloc(struct inode *inode,
> + const struct iomap *iomap, int nr_vecs, gfp_t gfp)
> +{
> + struct bio *bio;
> + struct block_device *bdev = iomap->bdev;
> +
> + if (!(iomap->flags & IOMAP_F_BEYOND_EOF) && fsverity_active(inode))
> + return iomap_fsverity_read_bio_alloc(inode, bdev, nr_vecs, gfp);
> +
> + bio = bio_alloc(bdev, nr_vecs, REQ_OP_READ, gfp);
> + if (bio)
> + bio->bi_end_io = iomap_read_end_io;
> + return bio;
> +}
> +
> static void iomap_bio_submit_read(struct iomap_read_folio_ctx *ctx)
> {
> struct bio *bio = ctx->read_ctx;
> @@ -42,26 +97,27 @@
> !bio_add_folio(bio, folio, plen, poff)) {
> gfp_t gfp = mapping_gfp_constraint(folio->mapping, GFP_KERNEL);
> gfp_t orig_gfp = gfp;
> - unsigned int nr_vecs = DIV_ROUND_UP(length, PAGE_SIZE);
>
> if (bio)
> submit_bio(bio);
>
> if (ctx->rac) /* same as readahead_gfp_mask */
> gfp |= __GFP_NORETRY | __GFP_NOWARN;
> - bio = bio_alloc(iomap->bdev, bio_max_segs(nr_vecs), REQ_OP_READ,
> - gfp);
> + bio = iomap_read_bio_alloc(iter->inode, iomap,
> + bio_max_segs(DIV_ROUND_UP(length, PAGE_SIZE)),
> + gfp);
> +
> /*
> * If the bio_alloc fails, try it again for a single page to
> * avoid having to deal with partial page reads. This emulates
> * what do_mpage_read_folio does.
> */
> if (!bio)
> - bio = bio_alloc(iomap->bdev, 1, REQ_OP_READ, orig_gfp);
> + bio = iomap_read_bio_alloc(iter->inode, iomap, 1,
> + orig_gfp);
> if (ctx->rac)
> bio->bi_opf |= REQ_RAHEAD;
> bio->bi_iter.bi_sector = sector;
> - bio->bi_end_io = iomap_read_end_io;
> bio_add_folio_nofail(bio, folio, plen, poff);
> ctx->read_ctx = bio;
> }
> diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
> index 79d1c97f02..481f7e1cff 100644
> --- a/fs/iomap/buffered-io.c
> +++ b/fs/iomap/buffered-io.c
> @@ -8,6 +8,7 @@
> #include <linux/writeback.h>
> #include <linux/swap.h>
> #include <linux/migrate.h>
> +#include <linux/fsverity.h>
> #include "internal.h"
> #include "trace.h"
>
> @@ -532,10 +533,19 @@
> if (plen == 0)
> return 0;
>
> + /* end of fs-verity region*/
> + if ((iomap->flags & IOMAP_F_BEYOND_EOF) && (iomap->type == IOMAP_HOLE)) {
Overly long line.
Also, when do we get the combination of BEYOND_EOF && HOLE? Is that for
sparse regions in only the merkle tree? IIRC (and I could be wrong)
fsverity still wants to checksum sparse holes in the regular file data,
right?
> + folio_zero_range(folio, poff, plen);
> + iomap_set_range_uptodate(folio, poff, plen);
> + }
> /* zero post-eof blocks as the page may be mapped */
> - if (iomap_block_needs_zeroing(iter, pos) &&
> + else if (iomap_block_needs_zeroing(iter, pos) &&
} else if (...
(nitpicking indentation)
> !(iomap->flags & IOMAP_F_BEYOND_EOF)) {
> folio_zero_range(folio, poff, plen);
> + if (fsverity_active(iter->inode) &&
> + !fsverity_verify_blocks(folio, plen, poff)) {
> + return -EIO;
> + }
> iomap_set_range_uptodate(folio, poff, plen);
> } else {
> if (!*bytes_submitted)
> diff --git a/fs/iomap/ioend.c b/fs/iomap/ioend.c
> index 86f44922ed..30c0de3c75 100644
> --- a/fs/iomap/ioend.c
> +++ b/fs/iomap/ioend.c
> @@ -9,6 +9,8 @@
> #include "internal.h"
> #include "trace.h"
>
> +#define IOMAP_POOL_SIZE (4 * (PAGE_SIZE / SECTOR_SIZE))
How do we arrive at this pool size? How is it important to have a
larger bio reserve pool for *larger* base page sizes?
--D
> +
> struct bio_set iomap_ioend_bioset;
> EXPORT_SYMBOL_GPL(iomap_ioend_bioset);
>
> @@ -423,9 +425,46 @@
> }
> EXPORT_SYMBOL_GPL(iomap_split_ioend);
>
> +#ifdef CONFIG_FS_VERITY
> +struct bio_set *iomap_fsverity_bioset;
> +EXPORT_SYMBOL_GPL(iomap_fsverity_bioset);
> +int iomap_fsverity_init_bioset(void)
> +{
> + struct bio_set *bs, *old;
> + int error;
> +
> + bs = kzalloc(sizeof(*bs), GFP_KERNEL);
> + if (!bs)
> + return -ENOMEM;
> +
> + error = bioset_init(bs, IOMAP_POOL_SIZE,
> + offsetof(struct iomap_fsverity_bio, bio),
> + BIOSET_NEED_BVECS);
> + if (error) {
> + kfree(bs);
> + return error;
> + }
> +
> + /*
> + * This has to be atomic as readaheads can race to create the
> + * bioset. If someone set the pointer before us, we drop ours.
> + */
> + old = cmpxchg(&iomap_fsverity_bioset, NULL, bs);
> + if (old) {
> + bioset_exit(bs);
> + kfree(bs);
> + }
> +
> + return 0;
> +}
> +EXPORT_SYMBOL_GPL(iomap_fsverity_init_bioset);
> +#else
> +# define iomap_fsverity_init_bioset(...) (-EOPNOTSUPP)
> +#endif
> +
> static int __init iomap_ioend_init(void)
> {
> - return bioset_init(&iomap_ioend_bioset, 4 * (PAGE_SIZE / SECTOR_SIZE),
> + return bioset_init(&iomap_ioend_bioset, IOMAP_POOL_SIZE,
> offsetof(struct iomap_ioend, io_bio),
> BIOSET_NEED_BVECS);
> }
> diff --git a/include/linux/iomap.h b/include/linux/iomap.h
> index 7a7e31c499..b451ab3426 100644
> --- a/include/linux/iomap.h
> +++ b/include/linux/iomap.h
> @@ -342,6 +342,17 @@
> iter->srcmap.type == IOMAP_MAPPED;
> }
>
> +#ifdef CONFIG_FS_VERITY
> +extern struct bio_set *iomap_fsverity_bioset;
> +
> +struct iomap_fsverity_bio {
> + struct work_struct work;
> + struct bio bio;
> +};
> +
> +int iomap_fsverity_init_bioset(void);
> +#endif
> +
> ssize_t iomap_file_buffered_write(struct kiocb *iocb, struct iov_iter *from,
> const struct iomap_ops *ops,
> const struct iomap_write_ops *write_ops, void *private);
>
> --
> - Andrey
>
>
next prev parent reply other threads:[~2026-01-12 22:35 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 14:49 [PATCH v2 0/23] fs-verity support for XFS with post EOF merkle tree Andrey Albershteyn
2026-01-12 14:49 ` [PATCH v2 1/22] fsverity: report validation errors back to the filesystem Darrick J. Wong
2026-01-13 1:29 ` Darrick J. Wong
2026-01-13 8:09 ` Christoph Hellwig
2026-01-13 10:27 ` Andrey Albershteyn
2026-01-13 17:52 ` Darrick J. Wong
2026-01-12 14:49 ` [PATCH v2 2/22] fsverity: expose ensure_fsverity_info() Andrey Albershteyn
2026-01-12 22:05 ` Darrick J. Wong
2026-01-12 14:50 ` [PATCH v2 3/22] iomap: introduce IOMAP_F_BEYOND_EOF Andrey Albershteyn
2026-01-12 22:18 ` Darrick J. Wong
2026-01-12 22:31 ` Darrick J. Wong
2026-01-13 10:39 ` Andrey Albershteyn
2026-01-13 8:12 ` Christoph Hellwig
2026-01-13 10:50 ` Andrey Albershteyn
2026-01-13 16:22 ` Christoph Hellwig
2026-01-13 17:57 ` Darrick J. Wong
2026-01-16 21:52 ` Matthew Wilcox
2026-01-17 2:11 ` Darrick J. Wong
2026-01-12 14:50 ` [PATCH v2 4/22] iomap: allow iomap_file_buffered_write() take iocb without file Andrey Albershteyn
2026-01-12 22:22 ` Darrick J. Wong
2026-01-13 8:15 ` Christoph Hellwig
2026-01-13 10:53 ` Andrey Albershteyn
2026-01-13 16:43 ` Matthew Wilcox
2026-01-14 4:49 ` Matthew Wilcox
2026-01-14 6:41 ` Christoph Hellwig
2026-01-14 16:43 ` Darrick J. Wong
2026-01-12 14:50 ` [PATCH v2 5/22] iomap: integrate fs-verity verification into iomap's read path Andrey Albershteyn
2026-01-12 22:35 ` Darrick J. Wong [this message]
2026-01-13 11:16 ` Andrey Albershteyn
2026-01-13 16:23 ` Christoph Hellwig
2026-01-13 8:19 ` Christoph Hellwig
2026-01-12 14:50 ` [PATCH v2 6/22] xfs: add fs-verity ro-compat flag Andrey Albershteyn
2026-01-12 14:50 ` [PATCH v2 7/22] xfs: add inode on-disk VERITY flag Andrey Albershteyn
2026-01-12 14:50 ` [PATCH v2 8/22] xfs: initialize fs-verity on file open and cleanup on inode destruction Andrey Albershteyn
2026-01-12 14:50 ` [PATCH v2 9/22] xfs: don't allow to enable DAX on fs-verity sealed inode Andrey Albershteyn
2026-01-12 14:51 ` [PATCH v2 10/22] xfs: disable direct read path for fs-verity files Andrey Albershteyn
2026-01-13 8:20 ` Christoph Hellwig
2026-01-13 11:22 ` Andrey Albershteyn
2026-01-12 14:51 ` [PATCH v2 11/22] xfs: add verity info pointer to xfs inode Andrey Albershteyn
2026-01-12 22:39 ` Darrick J. Wong
2026-01-13 8:21 ` Christoph Hellwig
2026-01-13 18:02 ` Darrick J. Wong
2026-01-14 6:43 ` Christoph Hellwig
2026-01-12 14:51 ` [PATCH v2 12/22] xfs: introduce XFS_FSVERITY_CONSTRUCTION inode flag Andrey Albershteyn
2026-01-12 22:42 ` Darrick J. Wong
2026-01-13 11:24 ` Andrey Albershteyn
2026-01-12 14:51 ` [PATCH v2 13/22] xfs: introduce XFS_FSVERITY_REGION_START constant Andrey Albershteyn
2026-01-12 22:46 ` Darrick J. Wong
2026-01-13 12:23 ` Andrey Albershteyn
2026-01-13 18:06 ` Darrick J. Wong
2026-01-14 6:47 ` Christoph Hellwig
2026-01-14 7:59 ` Andrey Albershteyn
2026-01-14 16:50 ` Darrick J. Wong
2026-01-12 14:51 ` [PATCH v2 14/22] xfs: disable preallocations for fsverity Merkle tree writes Andrey Albershteyn
2026-01-12 22:49 ` Darrick J. Wong
2026-01-12 14:51 ` [PATCH v2 15/22] xfs: add writeback and iomap reading of Merkle tree pages Andrey Albershteyn
2026-01-12 22:51 ` Darrick J. Wong
2026-01-13 8:23 ` Christoph Hellwig
2026-01-13 12:31 ` Andrey Albershteyn
2026-01-12 14:51 ` [PATCH v2 16/22] xfs: add fs-verity support Andrey Albershteyn
2026-01-12 23:05 ` Darrick J. Wong
2026-01-13 18:32 ` Andrey Albershteyn
2026-01-14 16:40 ` Darrick J. Wong
2026-01-16 14:52 ` Andrey Albershteyn
2026-01-12 14:51 ` [PATCH v2 17/22] xfs: add fs-verity ioctls Andrey Albershteyn
2026-01-12 14:52 ` [PATCH v2 18/22] xfs: advertise fs-verity being available on filesystem Darrick J. Wong
2026-01-12 14:52 ` [PATCH v2 19/22] xfs: check and repair the verity inode flag state Darrick J. Wong
2026-01-12 14:52 ` [PATCH v2 20/22] xfs: report verity failures through the health system Darrick J. Wong
2026-01-12 14:52 ` [PATCH v2 21/22] xfs: add fsverity traces Andrey Albershteyn
2026-01-12 23:07 ` Darrick J. Wong
2026-01-12 14:52 ` [PATCH v2 22/22] xfs: enable ro-compat fs-verity flag Andrey Albershteyn
2026-01-13 16:36 ` [PATCH v2 0/23] fs-verity support for XFS with post EOF merkle tree Matthew Wilcox
2026-01-13 18:45 ` Andrey Albershteyn
2026-01-14 5:00 ` Matthew Wilcox
2026-01-14 6:15 ` Darrick J. Wong
2026-01-14 8:20 ` Andrey Albershteyn
2026-01-14 9:53 ` Andrey Albershteyn
2026-01-14 16:42 ` Darrick J. Wong
2026-01-19 6:33 ` fsverity metadata offset, was: " Christoph Hellwig
2026-01-19 19:32 ` Eric Biggers
2026-01-19 19:58 ` Darrick J. Wong
2026-01-20 7:32 ` Christoph Hellwig
2026-01-20 11:44 ` Andrey Albershteyn
2026-01-20 17:34 ` Darrick J. Wong
2026-01-21 15:03 ` Christoph Hellwig
2026-01-19 20:00 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260112223555.GL15551@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@kernel.org \
--cc=aalbersh@redhat.com \
--cc=david@fromorbit.com \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox