On Wed, 25 Jun 2025, Damien Le Moal wrote: > >> Do you have a specific example in mind ? > > > > What happens if a bio that is larger than "BIO_MAX_VECS << PAGE_SHIFT" > > enters dm_split_and_process_bio? Where will the bio be split? I don't see > > it, but maybe I'm missing something. > > See patch 3 of the v3 I sent: dm_zone_bio_needs_split() and > dm_split_and_process_bio() have been modified to always endup with need_split == > true for zone write BIOs, and that causes a call to bio_split_to_limits(). So > dm-crypt will always see BIOs that are smaller than limits->max_hw_sectors, > which is set to BIO_MAX_VECS << PAGE_SECTORS_SHIFT in dm-crypt io_hint. So > dm-crypt can never see a write BIO that is larger than BIO_MAX_VECS << PAGE_SHIFT. OK. I acked the patches and I suppose that they will be sent through the block layer tree. Or - should I send them through the device mapper tree? Mikulas
