Red Hat Bugzilla – Bug 336601
bind segfaults when incorrectly configured to use dbus
Last modified: 2013-04-30 19:37:12 EDT
Description of problem: In certain situations when bind is configured to use
dbus, but the other dbus client it would be communicating with isn't present,
bind will segfault.
Version-Release number of selected component (if applicable):
Happens pretty much every time if the start order is wrong (which I think is
generally true if you've upgraded) and it's configured to use dbus.
Steps to Reproduce:
1. service bind start
Log messages that say:
Oct 17 13:58:47 localhost named: dbus_svc_add_filter failed
Oct 17 13:58:47 localhost named: dbus_mgr initialization failed. D-BUS
service is disabled.
Oct 17 13:58:47 localhost named: running
Oct 17 13:58:47 localhost kernel: named: segfault at 348c7da0 eip
0044c1ff esp b74e9240 error 6
first 3 log messages, then no segfault.
This actually seems to be caused by the error logging functions in bind's dbus
initialization code, which call va_start but not always va_end. I've attached a
patch which fixes the problem.
Created attachment 230311 [details]
fix va_start calls that don't call va_end
I'm not sure if your crash is caused by missing va_end but patch is correct.
I've removed statement which patches idnkit because this part is already
obsolete and We're using libidn for IDN support. Thanks for patch.
I've got next report which will be related to this. Could you test updated
package (http://kojiweb.fedoraproject.org/koji/taskinfo?taskID=202749) ASAP,
please? This issue should be fixed in F8 final.
Created attachment 233521 [details]
I see this after upgrading too, even with new build
# rpm -q bind dbus
See attached gdb session log.
*** This bug has been marked as a duplicate of 339191 ***