Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionStefan Hajnoczi
2016-08-15 11:22:57 UTC
Description of problem:
zhguo from QE hit the QEMU crash fixed in:
commit 9e0f5b8108e248b78444c9a2ec41a8309825736c
Author: Jason Wang <jasowang>
Date: Thu Mar 12 17:50:18 2015 +0800
virtio: validate the existence of handle_output before calling it
The fix isn't present in qemu-kvm RHEL 5, 6, or 7. QEMU jumps to 0x0 if
the guest sets up a vring that is unused by the device and then notifies
it.
How reproducible:
100%
Steps to Reproduce:
1. Install gcc and kernel-devel inside the guest
2. Build the kernel module: make -C /lib/modules/$(uname -r)/build M=$PWD
3. Enable kernel module: insmod handle-output.ko
Actual results:
QEMU crashes with a jump to 0x0.
Expected results:
QEMU does not crash and the following guest kernel message is printed to the console:
Trying to trigger crash...
Unsuccessful - QEMU is fixed!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2016-2585.html
Description of problem: zhguo from QE hit the QEMU crash fixed in: commit 9e0f5b8108e248b78444c9a2ec41a8309825736c Author: Jason Wang <jasowang> Date: Thu Mar 12 17:50:18 2015 +0800 virtio: validate the existence of handle_output before calling it The fix isn't present in qemu-kvm RHEL 5, 6, or 7. QEMU jumps to 0x0 if the guest sets up a vring that is unused by the device and then notifies it. How reproducible: 100% Steps to Reproduce: 1. Install gcc and kernel-devel inside the guest 2. Build the kernel module: make -C /lib/modules/$(uname -r)/build M=$PWD 3. Enable kernel module: insmod handle-output.ko Actual results: QEMU crashes with a jump to 0x0. Expected results: QEMU does not crash and the following guest kernel message is printed to the console: Trying to trigger crash... Unsuccessful - QEMU is fixed!