From 3e4c5a6261770bced301b5e74233e7866166ea5b Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Sun, 1 Jun 2025 21:35:14 +0200 Subject: clean up repository --- gitlab/issues_text/target_missing/host_missing/accel_missing/1460 | 5 ----- 1 file changed, 5 deletions(-) delete mode 100644 gitlab/issues_text/target_missing/host_missing/accel_missing/1460 (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/1460') diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1460 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1460 deleted file mode 100644 index fe07e0d50..000000000 --- a/gitlab/issues_text/target_missing/host_missing/accel_missing/1460 +++ /dev/null @@ -1,5 +0,0 @@ -block_load fails if last block is included in snapshot and block device isn't multiple of BLK_MIG_BLOCK_SIZE -Description of problem: -The `block_load` function in `migration/block.c` has a bug where `blk_pwrite` or `blk_pwrite_zeroes` always write `cluster_size` bytes. If the underlying device is not a multiple of `BLK_MIG_BLOCK_SIZE`, the write will fail with -EIO when trying to write past the end of the device, as `blk_check_byte_request` checks the length of the device. - -This can be fixed by ensuring that `cur_addr` + write length passed to `blk_pwrite`/`blk_pwrite_zeroes` never exceeds the total length of the block device. -- cgit 1.4.1