1 files changed, 78 insertions, 0 deletions
diff --git a/results/classifier/118/i386/1917184 b/results/classifier/118/i386/1917184
new file mode 100644
index 000000000..9ecfc4936
--- /dev/null
+++ b/results/classifier/118/i386/1917184
@@ -0,0 +1,78 @@
+i386: 0.872
+user-level: 0.775
+x86: 0.734
+hypervisor: 0.636
+peripherals: 0.635
+architecture: 0.575
+device: 0.504
+network: 0.492
+kernel: 0.436
+ppc: 0.419
+performance: 0.398
+graphic: 0.393
+socket: 0.393
+semantic: 0.376
+PID: 0.369
+KVM: 0.364
+VMM: 0.362
+files: 0.339
+virtual: 0.322
+vnc: 0.311
+assembly: 0.293
+debug: 0.286
+risc-v: 0.272
+register: 0.261
+boot: 0.245
+mistranslation: 0.244
+permissions: 0.229
+TCG: 0.201
+arm: 0.198
+
+qemu-user vm86() segfaults handling interrupt with ss:sp in same page as cs:ip
+
+When using qemu-i386 to run a program that uses vm86(), if the vm86 code calls an interrupt while cs:ip and ss:sp both point within the same page, do_int tries to write to the page while it is not writable, causing a segfault.
+
+qemu version 5.2.0, x86-64 host.
+
+
+
+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.
+
+
+Bug still present in latest master
+
+
+This is an automated cleanup. This bug report has been moved to QEMU's
+new bug tracker on gitlab.com and thus gets marked as 'expired' now.
+Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/314
+
+