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.
Hello,
new Coverity rescan found new potential defect in qemu-kvm. Look at:
qemu-kvm-0.12.1.2/block/mirror.c:290 at the function mirror_abort()
There is done check for 's' non-null pointer but on the following line there is
direct dereference. Note that I don't know what is the purpose of these lines
but This check is really suspicious and at least something goes wrong.
List of added defects is attached.
Pavel
Devel:
This error is mentioned just as a warning and it depends on you whether
it will be fixed. This defect can be not so dangerous and/or not so
prioritized to be fixed in 6.3 so feel free to move it to 6.4 or close it as
a NOTABUG if we don't need to fix it at all.
Quality engineering:
This issue was found by static analysis tool and we can't provide any
reproducer for it. We are able to rescan package once this problem is
fixed. Please check this as SanityOnly (just check that patches for the
issues and check if nothing unexpected was added by the commit). If you
want to check the new package with Coverity yourself, feel free to use
covscan tool (https://engineering.redhat.com/trac/CoverityScan/wiki/covscan).
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
No Documentation Needed
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.
http://rhn.redhat.com/errata/RHBA-2012-0746.html
Hello, new Coverity rescan found new potential defect in qemu-kvm. Look at: qemu-kvm-0.12.1.2/block/mirror.c:290 at the function mirror_abort() There is done check for 's' non-null pointer but on the following line there is direct dereference. Note that I don't know what is the purpose of these lines but This check is really suspicious and at least something goes wrong. List of added defects is attached. Pavel Devel: This error is mentioned just as a warning and it depends on you whether it will be fixed. This defect can be not so dangerous and/or not so prioritized to be fixed in 6.3 so feel free to move it to 6.4 or close it as a NOTABUG if we don't need to fix it at all. Quality engineering: This issue was found by static analysis tool and we can't provide any reproducer for it. We are able to rescan package once this problem is fixed. Please check this as SanityOnly (just check that patches for the issues and check if nothing unexpected was added by the commit). If you want to check the new package with Coverity yourself, feel free to use covscan tool (https://engineering.redhat.com/trac/CoverityScan/wiki/covscan).