diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/gemma3:12b/device/146 | 2 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/device/1460 | 6 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/device/1463 | 42 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/device/1464611 | 30 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/device/1465 | 2 |
5 files changed, 82 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/device/146 b/results/classifier/gemma3:12b/device/146 new file mode 100644 index 00000000..822fd275 --- /dev/null +++ b/results/classifier/gemma3:12b/device/146 @@ -0,0 +1,2 @@ + +macOS Guest Reading USB 3.0 Bus as USB 2.0 diff --git a/results/classifier/gemma3:12b/device/1460 b/results/classifier/gemma3:12b/device/1460 new file mode 100644 index 00000000..dcf6aea3 --- /dev/null +++ b/results/classifier/gemma3:12b/device/1460 @@ -0,0 +1,6 @@ + +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. diff --git a/results/classifier/gemma3:12b/device/1463 b/results/classifier/gemma3:12b/device/1463 new file mode 100644 index 00000000..798627ba --- /dev/null +++ b/results/classifier/gemma3:12b/device/1463 @@ -0,0 +1,42 @@ + +VM with ivshmem and host pci device does not boot +Description of problem: +The boot aborts early if ivshmem and host-pci devices are used at the same time. +Steps to reproduce: +1. use a recent host kernel => 6.1.8 +2. use qemu from bullseye-backports (7.2) +3. use a recent edk2 bios with 4M secure boot + SMM +4. add ivshmem with e.g.: -chardev socket,path=/tmp/shared_mem,id=shared_mem -device ivshmem-doorbell,chardev=shared_mem,vectors=1 +5. add a host-pci device to the VM +6. try to boot he VM +Additional information: +Observations: +always add ivshmem with: -chardev socket,path=/tmp/shared_mem,id=shared_mem -device ivshmem-doorbell,chardev=shared_mem,vectors=1 +- a) no host-pci device + edk2 with secure boot => works +- b) with host-pci device + non edk2 => works +- c) with host-pci device + edk2 with secure boot => does not work +- d) with host-pci device + edk2 with secure boot + but without ivshmem => works + + +I have compiled a debug version of qemu und added some prints to the linux kernel. + +Qemu log shows: +``` +2023-01-25T23:30:47.128716Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument +2023-01-25T23:30:47.128741Z qemu-system-x86_64: vfio_dma_map(0x55cee4bf7b20, 0x385000000000, 0x2000000, 0x7fd7253ff000) = -2 (No such file or directory) +qemu: hardware error: vfio: DMA mapping failed, unable to continue +``` + +Kernel log prints in vfio_iommu_iova_dma_valid@drivers/vfio/vfio_iommu_type1.c - if (start >= node->start && end <= node->end): +``` +[ 1156.241294] DEBUG valid 1048576 >= 0 && 2147483647 <= 4276092927 +[ 1156.269472] DEBUG valid 1048576 >= 0 && 2130706431 <= 4276092927 +[ 1156.477577] DEBUG valid 3221225472 >= 0 && 3229614079 <= 4276092927 +[ 1156.478889] DEBUG valid 3254779904 >= 0 && 3254845439 <= 4276092927 +[ 1156.481226] DEBUG valid 3254779904 >= 0 && 3255042047 <= 4276092927 +[ 1156.482864] DEBUG valid 3221225472 >= 0 && 3229614079 <= 4276092927 +[ 1156.502867] DEBUG valid 61916248539136 >= 0 && 61916282093567 <= 4276092927 +[ 1156.502870] DEBUG valid 61916248539136 >= 4277141504 && 61916282093567 <= 549755813887 +``` + +The vfio_dma_map ioctl request from qemu to the kernel seems to fail because 0x385000000000 from qemu is not in any iova range known by the kernel. diff --git a/results/classifier/gemma3:12b/device/1464611 b/results/classifier/gemma3:12b/device/1464611 new file mode 100644 index 00000000..c046f4bf --- /dev/null +++ b/results/classifier/gemma3:12b/device/1464611 @@ -0,0 +1,30 @@ + +4 * redundant conditions + + +1. + +[qemu/hw/block/nvme.c:355]: (style) Redundant condition: sqid. 'A && (!A || B)' is equivalent to 'A || B' + + if (!sqid || (sqid && !nvme_check_sqid(n, sqid))) { + +2. + +[qemu/hw/block/nvme.c:429]: (style) Redundant condition: cqid. 'A && (!A || B)' is equivalent to 'A || B' + + if (!cqid || (cqid && !nvme_check_cqid(n, cqid))) { + +3. + +[qemu/hw/tpm/tpm_passthrough.c:157]: (style) Redundant condition: tpm_pt.tpm_op_canceled. 'A && (!A || B)' is equivalent to 'A || B' + + if (!tpm_pt->tpm_op_canceled || + (tpm_pt->tpm_op_canceled && errno != ECANCELED)) { + +4. + +[qemu/target-arm/translate-a64.c:5729]: (style) Redundant condition: size<3. 'A && (!A || B)' is equivalent to 'A || B' + + if (size > 3 + || (size < 3 && is_q) + || (size == 3 && !is_q)) { \ No newline at end of file diff --git a/results/classifier/gemma3:12b/device/1465 b/results/classifier/gemma3:12b/device/1465 new file mode 100644 index 00000000..73617f41 --- /dev/null +++ b/results/classifier/gemma3:12b/device/1465 @@ -0,0 +1,2 @@ + +MBR/Partition table corruption/loss , probably related to virtual sata disks and backup |