public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
	"Darrick J. Wong" <djwong@kernel.org>,
	 Carlos Maiolino <cem@kernel.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	 Anuj Gupta <anuj20.g@samsung.com>,
	Kanchan Joshi <joshi.k@samsung.com>,
	 Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
	ntfs3@lists.linux.dev, linux-block@vger.kernel.org,
	 nvdimm@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	linux-xfs@vger.kernel.org
Subject: Re: (subset) support file system generated / verified integrity information v4
Date: Tue, 10 Mar 2026 11:16:25 +0100	[thread overview]
Message-ID: <20260310-beengt-galant-e82b95450cc5@brauner> (raw)
In-Reply-To: <177306794392.32482.9164747646721806111.b4-ty@kernel.dk>

On Mon, Mar 09, 2026 at 08:52:23AM -0600, Jens Axboe wrote:
> 
> On Mon, 23 Feb 2026 05:20:00 -0800, Christoph Hellwig wrote:
> > this series adds support to generate and verify integrity information
> > (aka T10 PI) in the file system, instead of the automatic below the
> > covers support that is currently used.
> > 
> > There two reasons for this:
> > 
> >   a) to increase the protection enveloped.  Right now this is just a
> >      minor step from the bottom of the block layer to the file system,
> >      but it is required to support io_uring integrity data passthrough in
> >      the file system similar to the currently existing support for block
> >      devices, which will follow next.  It also allows the file system to
> >      directly see the integrity error and act upon in, e.g. when using
> >      RAID either integrated (as in btrfs) or by supporting reading
> >      redundant copies through the block layer.
> >   b) to make the PI processing more efficient.  This is primarily a
> >      concern for reads, where the block layer auto PI has to schedule a
> >      work item for each bio, and the file system them has to do it again
> >      for bounce buffering.  Additionally the current iomap post-I/O
> >      workqueue handling is a lot more efficient by supporting merging and
> >      avoiding workqueue scheduling storms.
> > 
> > [...]
> 
> Applied, thanks!
> 
> [01/16] block: factor out a bio_integrity_action helper
>         commit: 7ea25eaad5ae3a6c837a3df9bdb822194f002565
> [02/16] block: factor out a bio_integrity_setup_default helper
>         commit: a936655697cd8d1bab2fd5189e2c33dd6356a266
> [03/16] block: add a bdev_has_integrity_csum helper
>         commit: 7afe93946dff63aa57c6db81f5eb43ac8233364e
> [04/16] block: prepare generation / verification helpers for fs usage
>         commit: 3f00626832a9f85fc5a04b25898157a6d43cb236
> [05/16] block: make max_integrity_io_size public
>         commit: 8c56ef10150ed7650cf4105539242c94c156148c
> [06/16] block: add fs_bio_integrity helpers
>         commit: 0bde8a12b5540572a7fd6d2867bee6de15e4f289
> [07/16] block: pass a maxlen argument to bio_iov_iter_bounce
>         commit: a9aa6045abde87b94168c3ba034b953417e27272

I've pulled the shared branch and also updated my base to v7.0-rc3 as
per Christoph's request in the other mail.

      reply	other threads:[~2026-03-10 10:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 13:20 support file system generated / verified integrity information v4 Christoph Hellwig
2026-02-23 13:20 ` [PATCH 01/16] block: factor out a bio_integrity_action helper Christoph Hellwig
2026-02-23 13:20 ` [PATCH 02/16] block: factor out a bio_integrity_setup_default helper Christoph Hellwig
2026-02-23 13:20 ` [PATCH 03/16] block: add a bdev_has_integrity_csum helper Christoph Hellwig
2026-02-23 13:20 ` [PATCH 04/16] block: prepare generation / verification helpers for fs usage Christoph Hellwig
2026-02-23 13:20 ` [PATCH 05/16] block: make max_integrity_io_size public Christoph Hellwig
2026-02-23 13:20 ` [PATCH 06/16] block: add fs_bio_integrity helpers Christoph Hellwig
2026-02-23 13:20 ` [PATCH 07/16] block: pass a maxlen argument to bio_iov_iter_bounce Christoph Hellwig
2026-02-23 13:20 ` [PATCH 08/16] iomap: refactor iomap_bio_read_folio_range Christoph Hellwig
2026-02-23 13:20 ` [PATCH 09/16] iomap: pass the iomap_iter to ->submit_read Christoph Hellwig
2026-02-23 13:20 ` [PATCH 10/16] iomap: only call into ->submit_read when there is a read_ctx Christoph Hellwig
2026-02-23 13:20 ` [PATCH 11/16] iomap: allow file systems to hook into buffered read bio submission Christoph Hellwig
2026-02-23 13:20 ` [PATCH 12/16] ntfs3: remove copy and pasted iomap code Christoph Hellwig
2026-02-23 16:27   ` Darrick J. Wong
2026-02-27 13:46   ` Konstantin Komarov
2026-03-03 15:21     ` Christoph Hellwig
2026-03-04  9:57       ` Konstantin Komarov
2026-02-23 13:20 ` [PATCH 13/16] iomap: add a bioset pointer to iomap_read_folio_ops Christoph Hellwig
2026-02-23 13:20 ` [PATCH 14/16] iomap: support ioends for buffered reads Christoph Hellwig
2026-02-23 13:20 ` [PATCH 15/16] iomap: support T10 protection information Christoph Hellwig
2026-02-23 13:20 ` [PATCH 16/16] xfs: " Christoph Hellwig
2026-03-02 10:11 ` support file system generated / verified integrity information v4 Christian Brauner
2026-03-02 13:48   ` Christoph Hellwig
2026-03-04 12:55     ` Christian Brauner
2026-03-09 14:52 ` (subset) " Jens Axboe
2026-03-10 10:16   ` Christian Brauner [this message]

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=20260310-beengt-galant-e82b95450cc5@brauner \
    --to=brauner@kernel.org \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=anuj20.g@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=joshi.k@samsung.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ntfs3@lists.linux.dev \
    --cc=nvdimm@lists.linux.dev \
    /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