| 2020-01-13 23:11:26 |
dann frazier |
bug |
|
|
added bug |
| 2020-01-13 23:11:37 |
dann frazier |
nominated for series |
|
Ubuntu Focal |
|
| 2020-01-13 23:11:37 |
dann frazier |
bug task added |
|
qemu (Ubuntu Focal) |
|
| 2020-01-13 23:11:37 |
dann frazier |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-01-13 23:11:37 |
dann frazier |
bug task added |
|
qemu (Ubuntu Bionic) |
|
| 2020-01-13 23:11:37 |
dann frazier |
nominated for series |
|
Ubuntu Disco |
|
| 2020-01-13 23:11:37 |
dann frazier |
bug task added |
|
qemu (Ubuntu Disco) |
|
| 2020-01-13 23:11:37 |
dann frazier |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-01-13 23:11:37 |
dann frazier |
bug task added |
|
qemu (Ubuntu Eoan) |
|
| 2020-01-13 23:42:40 |
dann frazier |
qemu (Ubuntu Bionic): status |
New |
In Progress |
|
| 2020-01-13 23:42:42 |
dann frazier |
qemu (Ubuntu Bionic): assignee |
|
dann frazier (dannf) |
|
| 2020-01-16 22:21:59 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2020-01-21 19:24:28 |
Rafael David Tinoco |
bug |
|
|
added subscriber Ubuntu Server |
| 2020-01-21 19:24:33 |
Rafael David Tinoco |
bug |
|
|
added subscriber Ubuntu Virtualisation team |
| 2020-01-21 19:24:35 |
Rafael David Tinoco |
bug |
|
|
added subscriber Rafael David Tinoco |
| 2020-01-22 06:22:23 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/377706 |
|
| 2020-01-22 13:49:43 |
Dan Streetman |
description |
[Impact]
QEMU crashes when passing through 8 GPU devices on an AMD Rome-based system which is configured (via BIOS) as a single NUMA domain.
[Test Case]
[Fix]
[Regression Risk] |
[Impact]
QEMU crashes when passing through 8 GPU devices on an AMD Rome-based system which is configured (via BIOS) as a single NUMA domain.
[Test Case]
[Fix]
the index into the bitmap array of batch_notify_vqs incremented itself by BITS_PER_LONG but then incorrectly indexed the unsigned long bitmap array by the full index value; when the number of vqs was under BITS_PER_LONG, the index was always 0, but once the number of vqs increased over BITS_PER_LONG, the bitmap array was indexed with (e.g. using BITS_PER_LONG == 64) bitmap[64] instead of bitmap[1]. Fix it to use the proper index by dividing the index counter by BITS_PER_LONG to get the bitmap array index.
[Regression Risk]
as this changes/fixes the index into an array, regressions would likely occur around notifications to the guest about virtio-blk device updates, or out-of-bounds errors in qemu itself, causing crash.
[Scope]
This is needed in b/e/f.
This bug was introduced by commit e21737ab150c2742dd94089017db96c472dd4b87 which was introduced in version 2.7.0, so this bug does not exist in Xenial or earlier.
This is fixed by commit 725fe5d10dbd4259b1853b7d253cef83a3c0d22a which is not yet in focal. |
|
| 2020-01-22 13:50:14 |
Dan Streetman |
description |
[Impact]
QEMU crashes when passing through 8 GPU devices on an AMD Rome-based system which is configured (via BIOS) as a single NUMA domain.
[Test Case]
[Fix]
the index into the bitmap array of batch_notify_vqs incremented itself by BITS_PER_LONG but then incorrectly indexed the unsigned long bitmap array by the full index value; when the number of vqs was under BITS_PER_LONG, the index was always 0, but once the number of vqs increased over BITS_PER_LONG, the bitmap array was indexed with (e.g. using BITS_PER_LONG == 64) bitmap[64] instead of bitmap[1]. Fix it to use the proper index by dividing the index counter by BITS_PER_LONG to get the bitmap array index.
[Regression Risk]
as this changes/fixes the index into an array, regressions would likely occur around notifications to the guest about virtio-blk device updates, or out-of-bounds errors in qemu itself, causing crash.
[Scope]
This is needed in b/e/f.
This bug was introduced by commit e21737ab150c2742dd94089017db96c472dd4b87 which was introduced in version 2.7.0, so this bug does not exist in Xenial or earlier.
This is fixed by commit 725fe5d10dbd4259b1853b7d253cef83a3c0d22a which is not yet in focal. |
[Impact]
QEMU crashes when passing through 8 GPU devices on an AMD Rome-based system which is configured (via BIOS) as a single NUMA domain.
[Test Case]
[Fix]
the index into the bitmap array of batch_notify_vqs incremented itself by BITS_PER_LONG but then incorrectly indexed the unsigned long bitmap array by the full index value; when the number of vqs was under BITS_PER_LONG, the index was always 0, but once the number of vqs increased over BITS_PER_LONG, the bitmap array was indexed with (e.g. using BITS_PER_LONG == 64) bitmap[64] instead of bitmap[1]. Fix it to use the proper index by dividing the index counter by BITS_PER_LONG to get the bitmap array index.
[Regression Risk]
as this changes/fixes the index into an array, regressions would likely occur around notifications to the guest about virtio-blk device updates, or out-of-bounds errors in qemu itself, causing crash.
[Scope]
This is needed in b/e/f.
This bug was introduced by commit e21737ab150c2742dd94089017db96c472dd4b87 which was introduced in version 2.7.0, so this bug does not exist in Xenial or earlier.
This is fixed by commit 725fe5d10dbd4259b1853b7d253cef83a3c0d22a which is not yet in focal, but per comment 3 is included in the pending MR for focal. |
|
| 2020-01-22 13:50:24 |
Dan Streetman |
qemu (Ubuntu Disco): status |
New |
Won't Fix |
|
| 2020-01-22 14:14:02 |
Dan Streetman |
tags |
|
block-proposed-bionic block-proposed-eoan sts |
|
| 2020-01-22 14:15:14 |
Dan Streetman |
description |
[Impact]
QEMU crashes when passing through 8 GPU devices on an AMD Rome-based system which is configured (via BIOS) as a single NUMA domain.
[Test Case]
[Fix]
the index into the bitmap array of batch_notify_vqs incremented itself by BITS_PER_LONG but then incorrectly indexed the unsigned long bitmap array by the full index value; when the number of vqs was under BITS_PER_LONG, the index was always 0, but once the number of vqs increased over BITS_PER_LONG, the bitmap array was indexed with (e.g. using BITS_PER_LONG == 64) bitmap[64] instead of bitmap[1]. Fix it to use the proper index by dividing the index counter by BITS_PER_LONG to get the bitmap array index.
[Regression Risk]
as this changes/fixes the index into an array, regressions would likely occur around notifications to the guest about virtio-blk device updates, or out-of-bounds errors in qemu itself, causing crash.
[Scope]
This is needed in b/e/f.
This bug was introduced by commit e21737ab150c2742dd94089017db96c472dd4b87 which was introduced in version 2.7.0, so this bug does not exist in Xenial or earlier.
This is fixed by commit 725fe5d10dbd4259b1853b7d253cef83a3c0d22a which is not yet in focal, but per comment 3 is included in the pending MR for focal. |
[Impact]
QEMU crashes when passing through 8 GPU devices on an AMD Rome-based system which is configured (via BIOS) as a single NUMA domain.
[Test Case]
[Fix]
the index into the bitmap array of batch_notify_vqs incremented itself by BITS_PER_LONG but then incorrectly indexed the unsigned long bitmap array by the full index value; when the number of vqs was under BITS_PER_LONG, the index was always 0, but once the number of vqs increased over BITS_PER_LONG, the bitmap array was indexed with (e.g. using BITS_PER_LONG == 64) bitmap[64] instead of bitmap[1]. Fix it to use the proper index by dividing the index counter by BITS_PER_LONG to get the bitmap array index.
[Regression Risk]
as this changes/fixes the index into an array, regressions would likely occur around notifications to the guest about virtio-blk device updates, or out-of-bounds errors in qemu itself, causing crash.
[Scope]
This is needed in b/e/f.
This bug was introduced by commit e21737ab150c2742dd94089017db96c472dd4b87 which was introduced in version 2.7.0, so this bug does not exist in Xenial or earlier.
This is fixed by commit 725fe5d10dbd4259b1853b7d253cef83a3c0d22a which is not yet in focal, but per comment 3 is included in the pending MR for focal.
[other info]
I added 'block-proposed' tags for b/e for this, to prevent release until after the patch has been released in focal. |
|
| 2020-01-22 16:03:08 |
dann frazier |
description |
[Impact]
QEMU crashes when passing through 8 GPU devices on an AMD Rome-based system which is configured (via BIOS) as a single NUMA domain.
[Test Case]
[Fix]
the index into the bitmap array of batch_notify_vqs incremented itself by BITS_PER_LONG but then incorrectly indexed the unsigned long bitmap array by the full index value; when the number of vqs was under BITS_PER_LONG, the index was always 0, but once the number of vqs increased over BITS_PER_LONG, the bitmap array was indexed with (e.g. using BITS_PER_LONG == 64) bitmap[64] instead of bitmap[1]. Fix it to use the proper index by dividing the index counter by BITS_PER_LONG to get the bitmap array index.
[Regression Risk]
as this changes/fixes the index into an array, regressions would likely occur around notifications to the guest about virtio-blk device updates, or out-of-bounds errors in qemu itself, causing crash.
[Scope]
This is needed in b/e/f.
This bug was introduced by commit e21737ab150c2742dd94089017db96c472dd4b87 which was introduced in version 2.7.0, so this bug does not exist in Xenial or earlier.
This is fixed by commit 725fe5d10dbd4259b1853b7d253cef83a3c0d22a which is not yet in focal, but per comment 3 is included in the pending MR for focal.
[other info]
I added 'block-proposed' tags for b/e for this, to prevent release until after the patch has been released in focal. |
[Impact]
QEMU crashes when passing through 8 GPU devices on an AMD Rome-based system which is configured (via BIOS) as a single NUMA domain.
[Test Case]
uvt-kvm create test
uvt-kvm wait test
uvt-kvm ssh test sudo poweroff
virsh edit test
# change:
# <driver name='qemu' type='qcow2'/>
# to:
# <driver name='qemu' type='qcow2' queues='128'/>
virsh start test
virsh console test
# QEMU will crash before booting into the kernel
[Fix]
the index into the bitmap array of batch_notify_vqs incremented itself by BITS_PER_LONG but then incorrectly indexed the unsigned long bitmap array by the full index value; when the number of vqs was under BITS_PER_LONG, the index was always 0, but once the number of vqs increased over BITS_PER_LONG, the bitmap array was indexed with (e.g. using BITS_PER_LONG == 64) bitmap[64] instead of bitmap[1]. Fix it to use the proper index by dividing the index counter by BITS_PER_LONG to get the bitmap array index.
[Regression Risk]
as this changes/fixes the index into an array, regressions would likely occur around notifications to the guest about virtio-blk device updates, or out-of-bounds errors in qemu itself, causing crash.
[Scope]
This is needed in b/e/f.
This bug was introduced by commit e21737ab150c2742dd94089017db96c472dd4b87 which was introduced in version 2.7.0, so this bug does not exist in Xenial or earlier.
This is fixed by commit 725fe5d10dbd4259b1853b7d253cef83a3c0d22a which is not yet in focal, but per comment 3 is included in the pending MR for focal.
[other info]
I added 'block-proposed' tags for b/e for this, to prevent release until after the patch has been released in focal. |
|
| 2020-01-27 14:42:45 |
Łukasz Zemczak |
qemu (Ubuntu Eoan): status |
New |
Fix Committed |
|
| 2020-01-27 14:42:47 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-01-27 14:42:49 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2020-01-27 14:42:52 |
Łukasz Zemczak |
tags |
block-proposed-bionic block-proposed-eoan sts |
block-proposed-bionic block-proposed-eoan sts verification-needed verification-needed-eoan |
|
| 2020-01-27 14:46:04 |
Łukasz Zemczak |
qemu (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-01-27 14:46:11 |
Łukasz Zemczak |
tags |
block-proposed-bionic block-proposed-eoan sts verification-needed verification-needed-eoan |
block-proposed-bionic block-proposed-eoan sts verification-needed verification-needed-bionic verification-needed-eoan |
|
| 2020-01-28 01:15:45 |
dann frazier |
bug watch added |
|
https://github.com/systemd/systemd/issues/8880 |
|
| 2020-01-28 14:59:45 |
dann frazier |
tags |
block-proposed-bionic block-proposed-eoan sts verification-needed verification-needed-bionic verification-needed-eoan |
block-proposed-bionic block-proposed-eoan sts verification-done-bionic verification-needed verification-needed-eoan |
|
| 2020-02-04 16:07:54 |
dann frazier |
tags |
block-proposed-bionic block-proposed-eoan sts verification-done-bionic verification-needed verification-needed-eoan |
block-proposed-bionic block-proposed-eoan sts verification-done verification-done-bionic verification-done-eoan |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
qemu (Ubuntu Focal): status |
New |
Fix Released |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2018-12126 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2018-12127 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2018-12130 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2018-19665 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2018-20123 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2018-20124 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2018-20125 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2018-20126 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2018-20191 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2018-20216 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2018-20815 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2019-11091 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2019-12068 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2019-13164 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2019-14378 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2019-15890 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2019-5008 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2019-8934 |
|
| 2020-02-06 20:45:52 |
Launchpad Janitor |
cve linked |
|
2019-9824 |
|
| 2020-02-06 21:23:30 |
dann frazier |
tags |
block-proposed-bionic block-proposed-eoan sts verification-done verification-done-bionic verification-done-eoan |
sts verification-done verification-done-bionic verification-done-eoan |
|
| 2020-02-06 21:24:04 |
dann frazier |
qemu (Ubuntu Bionic): assignee |
dann frazier (dannf) |
|
|
| 2020-02-11 22:49:20 |
Launchpad Janitor |
qemu (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2020-02-11 22:49:29 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-02-11 22:49:42 |
Launchpad Janitor |
qemu (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-05-25 13:22:19 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/qemu/+git/qemu/+merge/383566 |
|
| 2020-05-26 17:42:37 |
Launchpad Janitor |
merge proposal unlinked |
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/qemu/+git/qemu/+merge/383566 |
|
|
