summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/instruction/1460
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/105/instruction/1460')
-rw-r--r--results/classifier/zero-shot/105/instruction/146018
1 files changed, 18 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/105/instruction/1460 b/results/classifier/zero-shot/105/instruction/1460
new file mode 100644
index 000000000..938bbd658
--- /dev/null
+++ b/results/classifier/zero-shot/105/instruction/1460
@@ -0,0 +1,18 @@
+instruction: 0.836
+graphic: 0.762
+device: 0.725
+network: 0.655
+other: 0.628
+semantic: 0.604
+socket: 0.524
+vnc: 0.462
+KVM: 0.398
+mistranslation: 0.333
+boot: 0.244
+assembly: 0.222
+
+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.