On Wed, Nov 02, 2022 at 08:52:15AM -0600, Keith Busch wrote: > [Cc'ing Dmitrii, who also reported the same issue] > > On Tue, Nov 01, 2022 at 08:11:15PM -0700, Eric Biggers wrote: > > Hi, > > > > I happened to notice the following QEMU bug report: > > > > https://gitlab.com/qemu-project/qemu/-/issues/1290 > > > > I believe it's a regression from the following kernel commit: > > > > commit b1a000d3b8ec582da64bb644be633e5a0beffcbf > > Author: Keith Busch <kbusch@xxxxxxxxxx> > > Date: Fri Jun 10 12:58:29 2022 -0700 > > > > block: relax direct io memory alignment > > > > The bug is that if a dm-crypt device is set up with a crypto sector size (and > > thus also a logical_block_size) of 4096, then the block layer now lets through > > direct I/O requests to dm-crypt when the user buffer has only 512-byte > > alignment, instead of the 4096-bytes expected by dm-crypt in that case. This is > > because the dma_alignment of the device-mapper device is only 511 bytes. > > > > This has two effects in this case: > > > > - The error code for DIO with a misaligned buffer is now EIO, instead of > > EINVAL as expected and documented. This is because the I/O reaches > > dm-crypt instead of being rejected by the block layer. > > > > - STATX_DIOALIGN reports 512 bytes for stx_dio_mem_align, instead of the > > correct value of 4096. (Technically not a regression since STATX_DIOALIGN > > is new in v6.1, but still a bug.) > > > > Any thoughts on what the correct fix is here? Maybe the device-mapper layer > > needs to set dma_alignment correctly? Or maybe the block layer needs to set it > > to 'logical_block_size - 1' by default? > > I think the quick fix is to have the device mapper override the default > queue stacking limits to align the dma mask to logical block size. This is what I'm coming up with. Only compile tested (still setting up an enviroment to actually run it). --- diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c index 159c6806c19b..9334e58a4c9f 100644 --- a/drivers/md/dm-crypt.c +++ b/drivers/md/dm-crypt.c @@ -43,6 +43,7 @@ #include <linux/device-mapper.h> #include "dm-audit.h" +#include "dm-core.h" #define DM_MSG_PREFIX "crypt" @@ -3615,7 +3616,9 @@ static int crypt_iterate_devices(struct dm_target *ti, static void crypt_io_hints(struct dm_target *ti, struct queue_limits *limits) { + struct mapped_device *md = dm_table_get_md(ti->table); struct crypt_config *cc = ti->private; + struct request_queue *q = md->queue; /* * Unfortunate constraint that is required to avoid the potential @@ -3630,6 +3633,8 @@ static void crypt_io_hints(struct dm_target *ti, struct queue_limits *limits) limits->physical_block_size = max_t(unsigned, limits->physical_block_size, cc->sector_size); limits->io_min = max_t(unsigned, limits->io_min, cc->sector_size); + + blk_queue_dma_alignment(q, limits->logical_block_size - 1); } static struct target_type crypt_target = { -- -- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
