Message-ID: <421DDA37.7010300@folkwang-hochschule.de>
Date: Thu, 24 Feb 2005 14:44:23 +0100
From: Joern Nettingsmeier <nettings@folkwang-hochschule.de>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
MIME-Version: 1.0
To: bert hubert <ahu@ds9a.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FUTEX deadlock in ping?
References: <421DA915.7020209@uni-duisburg.de> <20050224120750.GA18677@outpost.ds9a.nl>
In-Reply-To: <20050224120750.GA18677@outpost.ds9a.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1260
Lines: 39

hi bert!

thanks for your reply.

bert hubert wrote:
> On Thu, Feb 24, 2005 at 11:14:45AM +0100, J?rn Nettingsmeier wrote:
> 
> 
>>ever since moving to ldap for passwd/group/shadow/hosts lookup, ping to 
>>a non-reachable host just freezes up and never returns:
>>
>>spunk:~ # strace ping herrnilsson
>>execve("/bin/ping", ["ping", "herrnilsson"], [/* 61 vars */]) = 0
>>uname({sys="Linux", node="spunk", ...}) = 0
>>brk(0)                                  = 0x8063000
>>...
>>...
>>munmap(0x40504000, 4096)                = 0
>>brk(0x80a5000)                          = 0x80a5000
>>uname({sys="Linux", node="spunk", ...}) = 0
>>futex(0x401540f4, FUTEX_WAIT, 2, NULL
>>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> 
> Try ping -n. This is most likely something else.
>

hmm. ping -n would still have to look up the hostname, and indeed the 
strace is identical (hanging). but when i ping the ip (this is probably 
what you had in mind), it works as expected.

anyway, why would a process block endlessly in a futex?


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/