On Mon, Nov 18, 2024 at 03:52:50PM +0100, Mikulas Patocka wrote: > > > On Mon, 18 Nov 2024, Mikulas Patocka wrote: > > > On Sat, 16 Nov 2024, dap581 wrote: > > > > > Hello, > > > Starting with kernel 6.11.x series up to current 6.12-rc7 > > > when I unlock my encrypted hdd (storage, not root) with cryptsetup: > > > > > > cryptsetup luksOpen /dev/sda1 hdd5 -d keyfile_hdd5 > > > > > > it triggers an alignment inconsistency: > > > In dmesg log, I read: > > > ---- > > > [ 105.841278] device-mapper: table: 254:1: adding target device sda1 > > > caused an alignment inconsistency: physical_block_size=4096, > > > logical_block_size=512, alignment_offset=0, start=16777216 > > > [ 105.841292] device-mapper: table: 254:1: adding target device sda1 > > > caused an alignment inconsistency: physical_block_size=4096, > > > logical_block_size=512, alignment_offset=0, start=16777216 > > > [ 105.841601] device-mapper: table: 254:1: adding target device sda1 > > > caused an alignment inconsistency: physical_block_size=4096, > > > logical_block_size=512, alignment_offset=0, start=16777216 > > > [ 105.841607] device-mapper: table: 254:1: adding target device sda1 > > > caused an alignment inconsistency: physical_block_size=4096, > > > logical_block_size=512, alignment_offset=0, start=16777216 > > > ---- > > Hi > > Does this patch fix it?
FYI, this rounding down looks reasonable to me: Reviewed-by: Christoph Hellwig <[email protected]>
