1 files changed, 72 insertions, 0 deletions
diff --git a/results/classifier/111/other/1893634 b/results/classifier/111/other/1893634
new file mode 100644
index 000000000..d585c48b8
--- /dev/null
+++ b/results/classifier/111/other/1893634
@@ -0,0 +1,72 @@
+other: 0.190
+device: 0.137
+semantic: 0.105
+graphic: 0.070
+files: 0.065
+network: 0.065
+PID: 0.062
+debug: 0.055
+performance: 0.055
+permissions: 0.050
+socket: 0.043
+KVM: 0.034
+vnc: 0.034
+boot: 0.033
+other: 0.162
+files: 0.159
+debug: 0.151
+semantic: 0.086
+PID: 0.085
+device: 0.079
+boot: 0.060
+network: 0.044
+performance: 0.039
+permissions: 0.032
+vnc: 0.031
+socket: 0.029
+graphic: 0.027
+KVM: 0.016
+
+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.]
+