On Mon, Jan 06, 2025 at 12:41:14PM +0000, John Garry wrote: > This series introduces initial device mapper atomic write support. > > Since we already support stacking atomic writes limits, it's quite > straightforward to support. > > Only dm-linear is supported for now, but other personalities could > be supported. > > Patch #1 is a proper fix, but the rest of the series is RFC - this is > because I have not fully tested and we are close to the end of this > development cycle. In general, looks reasonable. But I would prefer to see atomic write support added to dm-striped as well. Not that I have some need, but because it will help verify the correctness of the general stacking code changes (in both block and DM core). I wrote and/or fixed a fair amount of the non-atomic block limits stacking code over the years.. so this is just me trying to inform this effort based on limits stacking gotchas we've experienced to this point. Looks like adding dm-striped support would just need to ensure that the chunk_size is multiple of atomic write size (so chunk_size >= atomic write size). Relative to linear, testing limits stacking in terms of linear should also verify that concatenated volumes work. Thanks, Mike
