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.
Cause:
As part of initialization, spice server calls getaddrinfo(), so it can listen on socket(s) as provided in qemu-kvm command line.
When getaddrinfo failed (e.g. due to a "bad" addr= option), only a warning was issued.
Consequence:
Spice initialization (reds_init_socket) continued
and a call to getnameinfo() with bad parameters
resulted in a segfault.
Fix:
When getaddrinfo() fails, spice fails reds_init_socket
Result:
Upon bad network params (such as "addr") option, spice fails it's initialization and does not segfault.
Description of problem:
1. run qemu with '-spice addr=[ipv6::in:brackets],<rest_of_options>'
2. qemu segfaults in getnameinfo()
This may be a bug in spice server that should reject or correct the value of addr= or in getnameinfo() that should be able to cope with such address
Version-Release number of selected component:
qemu-kvm-0.12.1.2-2.355.el6
Additional info:
libreport version: 2.0.9
abrt_version: 2.0.8
backtrace_rating: 4
cmdline: qemu-kvm -monitor stdio -vga qxl -spice addr=[fe80::200:ff:fe00:0],disable-ticketing,x509-dir=/etc/pki/libvirt-spice,tls-port=5801,port=5800,tls-channel=main,tls-channel=inputs -incoming tcp:0:5701
crash_function: getnameinfo
kernel: 2.6.32-358.el6.x86_64
truncated backtrace:
:Thread no. 1 (7 frames)
: #0 getnameinfo at getnameinfo.c
: #1 reds_init_socket at reds.c
: #2 reds_init_net at reds.c
: #3 do_spice_init at reds.c
: #4 spice_server_init at reds.c
: #5 qemu_spice_init at /usr/src/debug/qemu-kvm-0.12.1.2/ui/spice-core.c
: #6 module_call_init at /usr/src/debug/qemu-kvm-0.12.1.2/module.c
Comment 11Pavel Šimerda (pavlix)
2013-03-06 11:22:22 UTC
I don't think spice should use getnameinfo() during initialization. Is there a valid reason for that? For any input from the user (including configuration), getaddrinfo() should be used to gather the necessary data.
During the initialization of a service, the only binary addressing data I could think of would come from the kernel through netlink. But these should rarely be used for any reverse lookup.
Comment 12Christophe Fergeau
2013-03-15 23:09:37 UTC
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-2013-1571.html