From: "Jörn Nettingsmeier" <pol-admin@uni-duisburg.de>
To: linux-kernel@vger.kernel.org
Cc: nettings@folkwang-hochschule.de
Subject: FUTEX deadlock in ping?
Date: Thu, 24 Feb 2005 11:14:45 +0100 [thread overview]
Message-ID: <421DA915.7020209@uni-duisburg.de> (raw)
hi !
disclaimer: i'm not a kernel guy ;)
after reading the FUTEX deadlock thread
(http://thread.gmane.org/gmane.linux.kernel/280900), i was wondering:
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
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
is this one related to the FUTEX problem olof described?
best,
jörn
ps: i'd appreciate being cc:ed on replies. thanks.
for the record:
spunk:~ # uname -a
Linux spunk 2.6.8-24.11-smp #1 SMP Fri Jan 14 13:01:26 UTC 2005 i686
i686 i386 GNU/Linux
SuSE 9.2
problem happens also on ia32 UP (same version as before) and amd64 UP
(2.6.11-rc4-bk7)
ldap lookup is ok, for instance
spunk:~ # getent hosts herrnilsson
192.168.0.3 herrnilsson.villakunterbunt.netz herrnilsson
traceroute and others work as well.
on an otherwise identical system without ldap, ping correctly gives
"unreachable" messages.
next reply other threads:[~2005-02-24 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 10:14 Jörn Nettingsmeier [this message]
2005-02-24 12:07 ` FUTEX deadlock in ping? bert hubert
2005-02-24 13:44 ` Joern Nettingsmeier
2005-02-24 14:46 ` Olof Johansson
2005-02-24 14:56 ` Jörn Nettingsmeier
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=421DA915.7020209@uni-duisburg.de \
--to=pol-admin@uni-duisburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nettings@folkwang-hochschule.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.