[Ubuntu18.04] qemu gets a trap when given a negative number to 'maxcpus' argument
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
Low
|
David Britton | ||
qemu (Ubuntu) |
Fix Released
|
Low
|
Christian Ehrhardt |
Bug Description
== Comment: #0 - NAGESWARA R. SASTRY <email address hidden> - 2017-08-28 02:18:19 ==
---Problem Description---
When passed a -ve number to 'maxcpus' parameter. Qemu stops with a trap
Contact Information = <email address hidden>
---uname output---
Linux ltc-boston25 4.13.0-
Machine Type = P9 Boston
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Run the following command.
P.S. maxcpus is provided with a negative number.
/usr/bin/
Userspace tool common name: /usr/bin/
The userspace tool has the following bit modes: 64-bit
Userspace rpm: qemu-kvm 1:2.10~
Userspace tool obtained from project website: na
*Additional Instructions for <email address hidden>:
-Attach ltrace and strace of userspace application.
P.S. Same issue seen on upstream with x86_64 and ppc64le architectures
Please pick
https:/
tags: | added: architecture-ppc64le bugnameltc-158060 severity-medium targetmilestone-inin1710 |
Changed in ubuntu: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
affects: | ubuntu → qemu (Ubuntu) |
Changed in ubuntu-power-systems: | |
assignee: | nobody → Canonical Server Team (canonical-server) |
importance: | Undecided → Medium |
Changed in ubuntu-power-systems: | |
status: | New → Confirmed |
tags: | added: triage-g |
Changed in qemu (Ubuntu): | |
assignee: | Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) → David Britton (davidpbritton) |
Changed in ubuntu-power-systems: | |
assignee: | Canonical Server Team (canonical-server) → David Britton (davidpbritton) |
tags: |
added: targetmilestone-inin1804 removed: targetmilestone-inin1710 |
Changed in ubuntu-power-systems: | |
importance: | Medium → Low |
Changed in ubuntu-power-systems: | |
status: | Confirmed → Fix Released |
Hi,
that is upstream commit [1].
I thank you for the report but this only makes a fatal error a nice-error-msg error.
It will be nice to pick this up with the next release of qemu, but that will be a no-op when we merge the new version for 18.04.
IMHO this is:
- bad user input leads to error (well that is normal right)
- not unbreaking a use case (one still gets an error, just a nicer one after the fix)
Therefore I'd consider this not important enough for any backport, but instead would track it as low prio task for the next release.
Please feel free to discuss if you disagree with that assessment.
[1]: https:/ /git.qemu. org/?p= qemu.git; a=commit; h=c0dd10991903c 552811d8cbe9231 055b1b3a7ebd