1 files changed, 73 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/kernel/1893634 b/results/classifier/zero-shot/118/kernel/1893634
new file mode 100644
index 000000000..f99221386
--- /dev/null
+++ b/results/classifier/zero-shot/118/kernel/1893634
@@ -0,0 +1,73 @@
+kernel: 0.945
+device: 0.894
+architecture: 0.853
+performance: 0.839
+peripherals: 0.820
+mistranslation: 0.800
+graphic: 0.799
+network: 0.791
+user-level: 0.741
+files: 0.717
+hypervisor: 0.712
+arm: 0.698
+permissions: 0.696
+x86: 0.692
+register: 0.686
+debug: 0.670
+PID: 0.663
+semantic: 0.651
+socket: 0.622
+TCG: 0.618
+i386: 0.603
+ppc: 0.601
+assembly: 0.587
+KVM: 0.576
+VMM: 0.574
+risc-v: 0.555
+virtual: 0.541
+boot: 0.535
+vnc: 0.531
+
+blk_get_max_transfer() works only with sg
+
+blk_get_max_transfer() is supposed to be able to get the max_sectors queue limit of the scsi device on the host side and is used in both scsi-generic.c (for scsi-generic and scsi-block) and scsi-disk.c (for scsi-hd) to set/change the max_xfer_len (and opt_xfer_len in the case of scsi-generic).
+
+However, it only works with the sg driver in doing so. It cannot get the queue limit with the sd driver and simply returns MAX_INT.
+
+qemu version 5.1.0
+kernel version 5.8.5
+
+Btw, is there a particular reason that it doesn't MIN_NON_ZERO against the original max_xfer_len: https://github.com/qemu/qemu/blob/v5.1.0/hw/scsi/scsi-generic.c#L172?
+
+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.]
+