From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: root=dhcp dhclient segfaulting on F-11
Date: Thu, 18 Jun 2009 10:34:20 +0200 [thread overview]
Message-ID: <4A39FC0C.8020305@bfh.ch> (raw)
In-Reply-To: <4A39F862.7060200-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Harald Hoyer wrote:
> On 06/18/2009 09:32 AM, Seewer Philippe wrote:
>>
>>
>> Warren Togami wrote:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=506626
>>>
>>> Filed the dhclient segfault here. I've been trying to debug this for
>>> the past 5 hours straight. I'm perplexed.
>>>
>>> Backing out to 1a945a576c0016c47f983d27727443ac33c5b6a8 prior to
>>> Phillippe's patch series dhclient does not crash.
>>
>> That is weird. I have no problems at all with isc-dhclient-V3.1.1
>>
>> Question: Does it segfault in the test-suites as well?
>>
>
> WORKSFORME
> fine with: dhclient-4.1.0-20.fc11.x86_64
I've not been able to reproduce the segfault.
But I've got the dhcp decline in vanilla isc dhclient-4.1.
Apparently dhclient-4.1 calls the dhclient-script twice with
reason BOUND. I have no idea why. But my dhclient-script has
(sadly) a small bug, which causes the dhclient to loop
endlessly and dhclient always declining.
Patch below fixes this, but I have absolutely no idea why.
diff --git a/modules.d/40network/dhclient-script b/modules.d/40network/dhclient-script
index 80ab54c..4153eb8 100755
--- a/modules.d/40network/dhclient-script
+++ b/modules.d/40network/dhclient-script
@@ -43,12 +43,12 @@ if getarg rdnetdebug ; then
set -x
fi
-# Huh? Interface configured?
-[ -f "/tmp/net.$netif.up" ] && exit 0
-
# We already need a set netif here
netif=$interface
+# Huh? Interface configured?
+[ -f "/tmp/net.$netif.up" ] && exit 0
+
case $reason in
PREINIT)
ip link set $netif up
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-18 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 16:18 root=dhcp broke Warren Togami
[not found] ` <4A391744.4040607-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-17 17:12 ` Seewer Philippe
[not found] ` <4A3923F7.6000900-omB+W0Dpw2o@public.gmane.org>
2009-06-17 17:15 ` Warren Togami
[not found] ` <4A3924B9.2090303-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-18 0:29 ` root=dhcp dhclient segfaulting on F-11 Warren Togami
[not found] ` <4A398A7C.40003-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-18 2:17 ` Warren Togami
[not found] ` <4A39A3D1.4070404-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-18 7:32 ` Seewer Philippe
[not found] ` <4A39ED97.8040503-omB+W0Dpw2o@public.gmane.org>
2009-06-18 8:18 ` Harald Hoyer
[not found] ` <4A39F862.7060200-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-18 8:34 ` Seewer Philippe [this message]
[not found] ` <4A39FC0C.8020305-omB+W0Dpw2o@public.gmane.org>
2009-06-18 11:30 ` Seewer Philippe
2009-06-18 7:32 ` Seewer Philippe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A39FC0C.8020305@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox