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.
