add 18th iteration of classifier

1 files changed, 216 insertions, 0 deletions

diff --git a/results/classifier/118/none/1077838 b/results/classifier/118/none/1077838
new file mode 100644
index 00000000..cd5b7bc3
--- /dev/null
+++ b/results/classifier/118/none/1077838
@@ -0,0 +1,216 @@
+permissions: 0.722
+semantic: 0.713
+user-level: 0.691
+hypervisor: 0.660
+peripherals: 0.619
+assembly: 0.614
+risc-v: 0.607
+TCG: 0.601
+KVM: 0.592
+architecture: 0.591
+VMM: 0.589
+register: 0.577
+graphic: 0.565
+device: 0.563
+mistranslation: 0.559
+debug: 0.554
+kernel: 0.545
+performance: 0.544
+virtual: 0.539
+ppc: 0.533
+arm: 0.528
+files: 0.516
+PID: 0.484
+vnc: 0.483
+i386: 0.446
+boot: 0.445
+x86: 0.357
+socket: 0.325
+network: 0.299
+
+qemu-nbd -r -c taints device for subsequent usage, even after -d
+
+Something about qemu-nbd -r -c /dev/nbd0 someimg leaves cruft behind - subsequent connections get marked readonly.
+
+This is on quantal, haven't checked precise or raring.
+
+To demonstrate:
+# use one image
+qemu-img create -f qcow2 /tmp/1.qcow2 100M
+sudo qemu-nbd -c /dev/nbd2 /tmp/1.qcow2
+sudo mkfs -t ext4 /dev/nbd2
+sudo qemu-nbd -d /dev/nbd2
+# use a second one on the same nbd device, shows that reuse works:
+qemu-img create -f qcow2 /tmp/2.qcow2 100M
+sudo qemu-nbd -c /dev/nbd2 /tmp/2.qcow2
+sudo mkfs -t ext4 /dev/nbd2
+sudo qemu-nbd -d /dev/nbd2
+# connect an image in read only mode
+sudo qemu-nbd -r -c /dev/nbd2 /tmp/2.qcow2
+sudo dumpe2fs /dev/nbd2 | head -n 3
+sudo qemu-nbd -d /dev/nbd2
+# now try to reuse in read-write mode again:
+qemu-img create -f qcow2 /tmp/3.qcow2 100M
+sudo qemu-nbd -c /dev/nbd2 /tmp/3.qcow2
+sudo mkfs -t ext4 /dev/nbd2
+# here it goes boom:
+mke2fs 1.42.5 (29-Jul-2012)
+/dev/nbd2: Operation not permitted while setting up superblock
+# still need to cleanup
+sudo qemu-nbd -d /dev/nbd2
+
+Happens on Precise as well.
+
+Quick code read - I think that this block:
+    if (flags & NBD_FLAG_READ_ONLY) {
+        int read_only = 1;       
+        TRACE("Setting readonly attribute");
+            
+        if (ioctl(fd, BLKROSET, (unsigned long) &read_only) < 0) { 
+            int serrno = errno;
+            LOG("Failed setting read-only attribute");
+            return -serrno;
+        }   
+    }       
+
+in nbd.c should be
+    {
+        int read_only = 0;
+        if (flags & NBD_FLAG_READ_ONLY)
+            read_only = 1;
+        TRACE("Setting readonly attribute");
+        if (ioctl(fd, BLKROSET, (unsigned long) &read_only) < 0) { 
+            int serrno = errno;
+            LOG("Failed setting read-only attribute");
+            return -serrno;
+        }   
+    }       
+
+
+http://paste.ubuntu.com/1352684/ is a debdiff, uploading the source format 3 patch as well
+
+
+
+
+
+Fixed patch - I had my sense inverted... http://paste.ubuntu.com/1352711/ 
+
+Thanks, this still applies upstream as well.
+
+To some extent it is a bug in the upstream kernel, which doesn't reset state properly. However, the qemu patch is also good. Thanks!
+
+Thanks, Paul, I'll cherrypick commit c8969eded252058e90e91f12f75f32aceae46ec9 into the ubuntu packages
+
+This bug was fixed in the package qemu-kvm - 1.2.0+noroms-0ubuntu4
+
+---------------
+qemu-kvm (1.2.0+noroms-0ubuntu4) raring; urgency=low
+
+  [ Serge Hallyn ]
+  * debian/qemu-kvm.postinst: use udevadm trigger to change /dev/kvm perms as
+    recommended by Steve Langasek (LP: #1057024)
+  * apply debian/patches/nbd-fixes-to-read-only-handling.patch from upstream to
+    make read-write mount after read-only mount work.  (LP: #1077838)
+
+  [ Robert Collins ]
+  * Fix upstart job to succeed if ksm settings can't be altered in the same way
+    other settings are handled. (LP: #1078530)
+ -- Serge Hallyn <email address hidden>   Wed, 14 Nov 2012 11:30:14 -0600
+
+Hello Robert, or anyone else affected,
+
+Accepted qemu-kvm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.0+noroms-0ubuntu14.4 in a few hours, and then in the -proposed repository.
+
+Please help us by testing this new package.  See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.  Your feedback will aid us getting this update out to other Ubuntu users.
+
+If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done.  If it does not, change the tag to verification-failed.  In either case, details of your testing will help us make a better decision.
+
+Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in advance!
+
+Hello Robert, or anyone else affected,
+
+Accepted qemu-kvm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.0+noroms-0ubuntu14.5 in a few hours, and then in the -proposed repository.
+
+Please help us by testing this new package.  See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.  Your feedback will aid us getting this update out to other Ubuntu users.
+
+If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done.  If it does not, change the tag to verification-failed.  In either case, details of your testing will help us make a better decision.
+
+Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in advance!
+
+Hello Robert, or anyone else affected,
+
+Accepted qemu-kvm into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.2.0+noroms-0ubuntu2.12.10.1 in a few hours, and then in the -proposed repository.
+
+Please help us by testing this new package.  See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.  Your feedback will aid us getting this update out to other Ubuntu users.
+
+If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done.  If it does not, change the tag to verification-failed.  In either case, details of your testing will help us make a better decision.
+
+Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in advance!
+
+Verified on precise.
+
+Verified on quantal.
+
+Hello Robert, or anyone else affected,
+
+Accepted qemu-kvm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qemu-kvm/1.0+noroms-0ubuntu14.6 in a few hours, and then in the -proposed repository.
+
+Please help us by testing this new package.  See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.  Your feedback will aid us getting this update out to other Ubuntu users.
+
+If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed.  In either case, details of your testing will help us make a better decision.
+
+Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in advance!
+
+Re-verified in precise.
+
+The verification of this Stable Release Update has completed successfully and the package has now been released to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report.  In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.
+
+This bug was fixed in the package qemu-kvm - 1.2.0+noroms-0ubuntu2.12.10.1
+
+---------------
+qemu-kvm (1.2.0+noroms-0ubuntu2.12.10.1) quantal-proposed; urgency=low
+
+  [ Serge Hallyn ]
+  * debian/qemu-kvm.postinst: use udevadm trigger to change /dev/kvm perms as
+    recommended by Steve Langasek (LP: #1057024)
+  * apply debian/patches/nbd-fixes-to-read-only-handling.patch from upstream to
+    make read-write mount after read-only mount work.  (LP: #1077838)
+  * make qemu-kvm depend on udev (LP: #1080912)
+
+  [ Robert Collins ]
+  * Fix upstart job to succeed if ksm settings can't be altered in the same way
+    other settings are handled. (LP: #1078530)
+ -- Serge Hallyn <email address hidden>   Mon, 19 Nov 2012 09:15:42 -0600
+
+This bug was fixed in the package qemu-kvm - 1.0+noroms-0ubuntu14.6
+
+---------------
+qemu-kvm (1.0+noroms-0ubuntu14.6) precise-proposed; urgency=low
+
+  * Fix qemu-kvm.upstart: just don't run in a container.  Otherwise we'll
+    still try to load/unload kernel modules.  Also undo the || true after
+    sysfs writes.  Since setting those is a part of configuring qemu-kvm
+    on the host, failing when they fail makes sense.
+
+qemu-kvm (1.0+noroms-0ubuntu14.5) precise-proposed; urgency=low
+
+  * add udev to qemu-kvm Depends to ensure that postinst succeeds.
+    (LP: #1080912)
+
+qemu-kvm (1.0+noroms-0ubuntu14.4) precise-proposed; urgency=low
+
+  [ Serge Hallyn ]
+  * debian/qemu-kvm.postinst: use udevadm trigger to change /dev/kvm perms as
+    recommended by Steve Langasek (LP: #1057024)
+  * apply debian/patches/nbd-fixes-to-read-only-handling.patch from upstream to
+    make read-write mount after read-only mount work.  (LP: #1077838)
+
+  [ Robert Collins ]
+  * Fix upstart job to succeed if ksm settings can't be altered in the same way
+    other settings are handled. (LP: #1078530)
+ -- Serge Hallyn <email address hidden>   Thu, 20 Dec 2012 12:34:52 -0600
+
+According to comment #9 this bug has been fixed by this commit here:
+http://git.qemu.org/?p=qemu.git;a=commitdiff;h=c8969eded252058
+... so I think it should be OK to close this bug now.
+