diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/118/device/150 | 31 | ||||
| -rw-r--r-- | results/classifier/118/device/1502 | 31 | ||||
| -rw-r--r-- | results/classifier/118/device/1507 | 67 |
3 files changed, 129 insertions, 0 deletions
diff --git a/results/classifier/118/device/150 b/results/classifier/118/device/150 new file mode 100644 index 00000000..95583ca7 --- /dev/null +++ b/results/classifier/118/device/150 @@ -0,0 +1,31 @@ +device: 0.877 +arm: 0.525 +graphic: 0.364 +semantic: 0.307 +mistranslation: 0.296 +i386: 0.265 +performance: 0.240 +risc-v: 0.234 +debug: 0.214 +x86: 0.213 +network: 0.197 +boot: 0.162 +architecture: 0.150 +ppc: 0.138 +kernel: 0.132 +permissions: 0.120 +virtual: 0.102 +KVM: 0.099 +vnc: 0.092 +files: 0.080 +socket: 0.067 +peripherals: 0.067 +register: 0.066 +user-level: 0.032 +assembly: 0.014 +TCG: 0.013 +VMM: 0.012 +PID: 0.011 +hypervisor: 0.004 + +Illegal Instruction with HVF when encountering SSE instructions in the emulator diff --git a/results/classifier/118/device/1502 b/results/classifier/118/device/1502 new file mode 100644 index 00000000..725422a4 --- /dev/null +++ b/results/classifier/118/device/1502 @@ -0,0 +1,31 @@ +device: 0.909 +user-level: 0.872 +performance: 0.650 +graphic: 0.575 +debug: 0.345 +arm: 0.313 +network: 0.300 +assembly: 0.240 +architecture: 0.223 +boot: 0.193 +semantic: 0.180 +PID: 0.175 +mistranslation: 0.168 +register: 0.142 +permissions: 0.122 +peripherals: 0.081 +files: 0.062 +kernel: 0.057 +hypervisor: 0.055 +socket: 0.049 +VMM: 0.046 +ppc: 0.035 +TCG: 0.031 +virtual: 0.031 +vnc: 0.031 +x86: 0.018 +i386: 0.016 +KVM: 0.008 +risc-v: 0.007 + +Usermode qemu-m68k futex crash while running "cmake -E cmake_autogen" diff --git a/results/classifier/118/device/1507 b/results/classifier/118/device/1507 new file mode 100644 index 00000000..b988c323 --- /dev/null +++ b/results/classifier/118/device/1507 @@ -0,0 +1,67 @@ +device: 0.942 +performance: 0.922 +files: 0.913 +graphic: 0.898 +PID: 0.896 +socket: 0.848 +network: 0.827 +ppc: 0.822 +architecture: 0.814 +semantic: 0.798 +mistranslation: 0.788 +kernel: 0.778 +vnc: 0.751 +register: 0.745 +peripherals: 0.706 +TCG: 0.692 +debug: 0.686 +x86: 0.677 +hypervisor: 0.656 +user-level: 0.652 +VMM: 0.652 +permissions: 0.648 +risc-v: 0.630 +arm: 0.629 +boot: 0.624 +i386: 0.616 +KVM: 0.584 +assembly: 0.467 +virtual: 0.462 + +export/fuse/fuse.c:fuse_fallocate does not do anything but returns success +Description of problem: +block/export/fuse.c:fuse_fallocate with `FALLOC_FL_PUNCH_HOLE` does not do anything even though it returns 0 (success). A later read incorrectly returns old data instead of zeros. +Should probably return EOPNOTSUPP. + +FALLOC_FL_PUNCH_HOLE: +>Within the specified range, partial filesystem blocks are zeroed, +and whole filesystem blocks are removed from the file. After a +successful call, subsequent reads from this range will return +zeros. +https://man7.org/linux/man-pages/man2/fallocate.2.html +Steps to reproduce: +```sh +touch /tmp/data /tmp/fuse_exp +dd if=/dev/random of=/tmp/data count=1000 bs=1M +qemu-storage-daemon --blockdev node-name=node0,driver=raw,file.driver=file,file.filename=/tmp/data --export type=fuse,id=node0-export,node-name=node0,mountpoint=/tmp/fuse_exp,writable=on + +hexdump /tmp/fuse_exp -n 16 +# 0000000 4d5f db2d 57ab 02f6 f9c2 d2f1 0c1b 4b86 +fallocate -l 1G --punch-hole /tmp/fuse_exp +echo $? +# 0 +hexdump /tmp/fuse_exp -n 16 +# 0000000 4d5f db2d 57ab 02f6 f9c2 d2f1 0c1b 4b86 + + +hexdump /tmp/data -n 16 +# 0000000 4d5f db2d 57ab 02f6 f9c2 d2f1 0c1b 4b86 +fallocate -l 1G --punch-hole /tmp/data +hexdump /tmp/data -n 16 +# 0000000 0000 0000 0000 0000 0000 0000 0000 0000 + +# sudo bpftrace -e 'uretprobe:/usr/bin/qemu-storage-daemon:blk_co_pdiscard { printf("ret=%d\n",retval); }' +# ret=0 +# sudo bpftrace -e 'kretfunc:fuse_file_fallocate { printf("len=%d \t mode=%d ret=%d\n", args->length , args->mode,retval); }' +# len=1073741824 mode=3 ret=0 +``` |