Bug 971904
| Summary: | libvirtd crashes on startup with udev_log="debug" in /etc/udev/udev.conf | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Ján Tomko <jtomko> |
| Component: | libvirt | Assignee: | Ján Tomko <jtomko> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4 | CC: | acathrow, dallan, dyuan, lnovich, ydu, zhwang |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-0.10.2-19.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Libvirt's logging function that was passed to libudev didn't handle strings with multiple parameters correctly.
Consequence: Libvirtd could crash when libudev logged a message.
Fix: Handle multiple parameters correctly.
Result: Libvirtd doesn't crash when libudev logs messages.
|
Story Points: | --- |
| Clone Of: | 969152 | Environment: | |
| Last Closed: | 2013-11-21 09:02:32 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 969152 | ||
| Bug Blocks: | |||
|
Description
Ján Tomko
2013-06-07 14:21:59 UTC
Fix is now committed upstream:
commit f753dd62f951cc62e164421d0c6491f39e4c68ad
Author: Ján Tomko <jtomko>
AuthorDate: 2013-06-07 11:55:27 +0200
Commit: Ján Tomko <jtomko>
CommitDate: 2013-06-14 13:17:27 +0200
udev: fix crash in libudev logging
Call virLogVMessage instead of virLogMessage, since libudev
called us with a va_list object, not a list of arguments.
Honor message priority and strip the trailing newline.
https://bugzilla.redhat.com/show_bug.cgi?id=969152
git describe: v1.0.6-76-gf753dd6
And posted downstream:
http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-June/msg00259.html
Verify this bug on libvirt libvirt-0.10.2-19.el6.x86_64 1.set the udev_log="debug" in /etc/udev/udev.conf 2.restart the libvirtd service #service libvirtd restart 3.check the service status # virsh list Id Name State ---------------------------------------------------- 1 rhelguest1 running # ps aux|grep libvirtd root 3083 0.0 0.0 1037828 14780 ? Sl 14:16 0:00 libvirtd --daemon # service libvirtd status libvirtd (pid 3083) is running... 4.set the udev_log="error","udev_log=info" , udev_log="warning" or udev_log=$invalid value in the /etc/udev/udev.conf,then do the step 2,we can get the same result with step 3 Also I can reproduce this bug on libvirt-0.10.2-18 1.set the udev_log="debug" in /etc/udev/udev.conf 2.restart the libvirtd service 3.check the service status # ps aux|grep libvirtd root 3675 0.0 0.0 103244 828 pts/0 S+ 14:49 0:00 grep libvirtd # service libvirtd status libvirtd dead but pid file exists Since this issue works well in libvirt 0.10.2-19, also i can reproduce it on libvirt-0.10.2-18, so mark this bug verified 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-1581.html |