This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu7.12
---
qemu (1:2.11+dfsg-1ubuntu7.12) bionic-security; urgency=medium
[ Marc Deslauriers ]
* SECURITY UPDATE: TOCTTOU in MTP
- debian/patches/CVE-2018-16872.patch: use O_NOFOLLOW and O_CLOEXEC in
I already verified it since that is very easy to do.
Setting verified.
But the actual release might be done through a security update which we
bundled with this change.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
Hello Matt, or anyone else affected,
Accepted qemu into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.11+dfsg-
1ubuntu7.11 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
After long back and forth on the 2.11.2 bug it is dead now :-/
I decoupled this fix and put it for SRU Team review into bionic-
unapproved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818264
This bug was fixed in the package qemu - 1:2.12+dfsg-3ubuntu8.4
---
qemu (1:2.12+dfsg-3ubuntu8.4) cosmic; urgency=medium
* fix crash when performing block pull on partial cluster (LP: #1818264)
- d/p/ubuntu/lp-1818264-block-Fix-copy-on-read-crash-with-partial.patch
--
Before upgrade:
root@c:~# qemu-img create -f qcow2 test 1024 2>&1
Formatting 'test', fmt=qcow2 size=1024 cluster_size=65536 lazy_refcounts=off
refcount_bits=16
root@c:~# qemu-io -f qcow2 -C -c 'read 0 1024' test
qemu-io: /build/qemu-w2bpg6/qemu-2.12+dfsg/block/io.c:1098:
Hello DevPump, or anyone else affected,
Accepted qemu into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.12+dfsg-
3ubuntu8.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Tested and working fine from PPA.
@SRU Team - FYI Cosmic up for review in -unapproved, Bionic intentionally not
yet - but that way around ordering should be fine.
- For Cosmic this can already be uploaded (where it is the only change).
- for Bionic the fix is bundled with the 2.11.2 changes
There is a test PPA [1] available that we can use to pre-check this
before the actual SRU.
[1]: https://launchpad.net/~paelzer/+archive/ubuntu/qemu-
bionic-1815477-1818264
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Applies fine, tomorrow I'll create PPAs to test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818264
Title:
QEMU 2.11.1 VM crash when performing block pull.
bdrv_co_do_copy_on_readv
To manage
Thanks, that looks good.
I can confirm the test and updated the bug description.
I'll check backportability for 2.11 and 2.12 later today after I have added
2.11.2
** Description changed:
+ [Impact]
+
+ * During qemu-io VM disk read, there is a possibility for qemu-io to
+abort crashing
** Changed in: qemu (Ubuntu)
Status: Incomplete => Triaged
** Also affects: qemu (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: Triaged => Fix
[Impact]
During qemu-io VM disk read, there is a possibility for qemu-io to abort
crashing the process running. This also crashes the VM the read is
running against.
[Test Case]
Steps to reproduce outside of a block pull:
# qemu-img create -f qcow2 test 1024 2>&1
# qemu-io -f qcow2 -C -c 'read
@DevPump - I think I can work on that along a general 2.11.2 upgrade which is
comming sooner or later.
But I'd need you to provide some good steps on how to recreate and test/verify
this to make [1] look usable on this bugs description.
Do you think you could provide as much as you can of [1]
14 matches
Mail list logo
