Rob Norris 63bafe60ec vdev_disk: try harder to ensure IO alignment rules ... It seems out our notion of "properly" aligned IO was incomplete. In particular, dm-crypt does its own splitting, and assumes that a logical block will never cross an order-0 page boundary (ie, the physical page size, not compound size). This effectively means that it needs to be possible to split a BIO at any page or block size boundary and have it work correctly. This updates the alignment check function to enforce these rules (to the extent possible). Our response to misaligned data is to make some new allocation that is properly aligned, and copy the data into it. It turns out that linearising (via abd_borrow_buf()) is not enough, because we allocate eg 4K blocks from a general purpose slab, and so may receive (or already have) a 4K block that crosses pages. So instead, we allocate a new ABD, which is guaranteed to be aligned properly to block sizes, and then copy everything into it, and back out on the way back. Sponsored-by: Klara, Inc. Sponsored-by: Wasabi Technology, Inc. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Alexander Motin <mav@FreeBSD.org> Reviewed-by: Tony Hutter <hutter2@llnl.gov> Signed-off-by: Rob Norris <rob.norris@klarasystems.com> Closes #16687 #16631 #15646 #15533 #14533		2024-10-31 17:00:42 -07:00
..
callbacks	Split functional testings via github action matrix	2023-03-15 10:41:05 -07:00
cmd	Always validate checksums for Direct I/O reads	2024-10-09 12:28:08 -07:00
include	ZTS: Add LUKS sanity test	2024-10-25 09:07:44 -07:00
tests	vdev_disk: try harder to ensure IO alignment rules	2024-10-31 17:00:42 -07:00
.gitignore	autoconf: use include directives instead of recursing down cmd	2022-05-10 10:18:38 -07:00
Makefile.am	tests: add test for vdev_disk page alignment check	2024-04-11 14:42:46 -07:00