From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 99671] New: glibc deadlock in __check_pf() presumed due to missing netlink response
Date: Tue, 9 Jun 2015 17:04:34 -0700 [thread overview]
Message-ID: <20150609170434.1eeec625@urahara> (raw)
Begin forwarded message:
Date: Mon, 8 Jun 2015 21:20:23 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 99671] New: glibc deadlock in __check_pf() presumed due to missing netlink response
https://bugzilla.kernel.org/show_bug.cgi?id=99671
Bug ID: 99671
Summary: glibc deadlock in __check_pf() presumed due to missing
netlink response
Product: Networking
Version: 2.5
Kernel Version: 4.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: shemminger@linux-foundation.org
Reporter: dwmw2@infradead.org
Regression: No
I keep seeing multithreaded processes deadlocked on glibc's __check_pf
function, with the culprit stuck like this:
#0 0x0000003841302edd in recvmsg () at ../sysdeps/unix/syscall-template.S:81
#1 0x000000384131f8ee in __check_pf (pid=-52599, fd=20) at
../sysdeps/unix/sysv/linux/check_pf.c:166
#2 0x000000384131f8ee in __check_pf (seen_ipv4=seen_ipv4@entry=0x7f5b137fdc32,
seen_ipv6=seen_ipv6@entry=0x7f5b137fdc33, in6ai=in6ai@entry=0x7f5b137fdc40,
in6ailen=in6ailen@entry=0x7f5b137fdc48) at
../sysdeps/unix/sysv/linux/check_pf.c:324
I don't understand why the glibc code is waiting; even if netlink responses are
dropped, it should get ENOBUFS and bail out.
This started happening to me, sporadically, when I updated my Fedora 22 beta
installation to the 4.0 kernel. It seemed to go away when I reverted to 3.19,
and came back again when I went back to 4.0. Filed in Red Hat bugzilla as
https://bugzilla.redhat.com/show_bug.cgi?id=1209433 and reported upstream at
https://www.marc.info/?l=linux-netdev&m=142849461211078&w=3 and
https://www.marc.info/?l=linux-netdev&m=142954024310299&w=3
Others seem to have seen it on earlier kernels though:
https://github.com/nahi/httpclient/issues/232
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2015-06-10 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 0:04 Stephen Hemminger [this message]
2015-06-10 0:46 ` Fw: [Bug 99671] New: glibc deadlock in __check_pf() presumed due to missing netlink response Eric Dumazet
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=20150609170434.1eeec625@urahara \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.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