1 files changed, 58 insertions, 0 deletions
diff --git a/results/classifier/108/other/1918149 b/results/classifier/108/other/1918149
new file mode 100644
index 00000000..dd59acc7
--- /dev/null
+++ b/results/classifier/108/other/1918149
@@ -0,0 +1,58 @@
+other: 0.893
+network: 0.738
+device: 0.734
+performance: 0.715
+debug: 0.687
+files: 0.685
+semantic: 0.637
+permissions: 0.635
+graphic: 0.622
+PID: 0.566
+vnc: 0.565
+socket: 0.546
+boot: 0.479
+KVM: 0.401
+
+qemu-user reports wrong fault_addr in signal handler
+
+When a SEGV signal occurs and si_addr of the info struct is nil, qemu still tries to translate the address from host to guest (handle_cpu_signal in accel/tcg/user-exec.c). This means, that the actual signal handler, will receive a fault_addr that is something like 0xffffffffbf709000.
+
+I was able to get this to happen, by branching to a non canonical address on aarch64.
+I used 5.2 (commit: 553032db17). However, building from source, this only seems to happen, if I use the same configure flags as the debian build:
+
+../configure --static --target-list=aarch64-linux-user --disable-system --enable-trace-backends=simple --disable-linux-io-uring  --disable-pie --extra-cflags="-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2"  --extra-ldflags="-Wl,-z,relro -Wl,--as-needed"
+
+Let me know, if you need more details.
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+