From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Stefan Priebe <s.priebe@profihost.ag>,
Florian Weimer <fweimer@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Asterisk deadlocks since Kernel 4.1
Date: Wed, 18 Nov 2015 22:40:27 +0100 [thread overview]
Message-ID: <1447882827.575319.443677441.6F45D05F@webmail.messagingengine.com> (raw)
In-Reply-To: <564CEF5D.3080005@profihost.ag>
On Wed, Nov 18, 2015, at 22:36, Stefan Priebe wrote:
> sorry here it is. What I'm wondering is why is there ipv6 stuff? I don't
> have ipv6 except for link local. Could it be this one?
>
> https://bugzilla.redhat.com/show_bug.cgi?id=505105#c79
>
> Thread 31 (Thread 0x7f295c011700 (LWP 26654)):
> #0 0x00007f295de3287d in recvmsg () at
> ../sysdeps/unix/syscall-template.S:82
> #1 0x00007f295de52fcc in make_request (fd=35, pid=26631,
> seen_ipv4=<optimized out>, seen_ipv6=<optimized out>,
> in6ai=<optimized out>, in6ailen=<optimized out>) at
> ../sysdeps/unix/sysv/linux/check_pf.c:119
> #2 0x00007f295de5344a in __check_pf (seen_ipv4=0x7f295c00e85f,
> seen_ipv6=0x7f295c00e85e, in6ai=0x7f295c00e840,
> in6ailen=0x7f295c00e838) at
> ../sysdeps/unix/sysv/linux/check_pf.c:271
> #3 0x00007f295de10007 in *__GI_getaddrinfo (name=0x7f295c00e8b0
> "10.12.12.55", service=0x7f295c00e8bc "2135",
> hints=0x7f295c00e910, pai=0x7f295c00e908) at
> ../sysdeps/posix/getaddrinfo.c:2389
Can you also get a /proc/pid/stack stacktrace?
Thanks,
Hannes
next prev parent reply other threads:[~2015-11-18 21:40 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <564B3D35.50004@profihost.ag>
[not found] ` <alpine.DEB.2.11.1511171936030.3761@nanos>
2015-11-17 19:27 ` Asterisk deadlocks since Kernel 4.1 Stefan Priebe
2015-11-17 19:43 ` Thomas Gleixner
2015-11-18 20:23 ` Stefan Priebe
2015-11-18 21:00 ` Hannes Frederic Sowa
2015-11-18 21:20 ` Stefan Priebe
2015-11-18 21:22 ` Hannes Frederic Sowa
2015-11-19 9:35 ` Stefan Priebe - Profihost AG
2015-11-18 21:18 ` Florian Weimer
2015-11-18 21:23 ` Stefan Priebe
2015-11-19 9:39 ` Florian Weimer
2015-11-18 21:36 ` Stefan Priebe
2015-11-18 21:40 ` Hannes Frederic Sowa [this message]
2015-11-18 21:42 ` Stefan Priebe
2015-11-18 21:58 ` Hannes Frederic Sowa
2015-11-19 9:44 ` Florian Weimer
2015-11-19 9:49 ` Stefan Priebe - Profihost AG
2015-11-19 9:56 ` Stefan Priebe - Profihost AG
2015-11-19 11:41 ` Hannes Frederic Sowa
2015-11-19 11:43 ` Stefan Priebe - Profihost AG
2015-11-19 12:41 ` Hannes Frederic Sowa
2015-11-19 12:46 ` Stefan Priebe - Profihost AG
2015-11-19 13:19 ` Florian Weimer
2015-11-19 19:51 ` Stefan Priebe
2015-11-23 12:44 ` Stefan Priebe - Profihost AG
2015-11-23 12:57 ` Hannes Frederic Sowa
2015-11-24 13:35 ` Stefan Priebe - Profihost AG
2015-12-02 9:45 ` Stefan Priebe - Profihost AG
2015-12-02 11:40 ` Hannes Frederic Sowa
2015-12-02 17:51 ` Philipp Hahn
2015-12-03 8:23 ` Stefan Priebe - Profihost AG
2015-12-04 18:26 ` Stefan Priebe
2015-12-05 1:08 ` Herbert Xu
2015-12-06 20:56 ` Stefan Priebe
2015-12-07 1:20 ` Herbert Xu
2015-12-07 6:58 ` Stefan Priebe - Profihost AG
2015-12-08 6:13 ` netlink: Add missing goto statement to netlink_insert Herbert Xu
2015-12-08 16:21 ` David Miller
2015-12-09 3:29 ` Greg KH
2015-12-07 7:41 ` Asterisk deadlocks since Kernel 4.1 Philipp Hahn
2015-12-05 14:19 ` Philipp Matthias Hahn
2015-12-05 15:34 ` Stefan Priebe
2015-12-02 17:15 ` Philipp Hahn
2015-12-02 18:23 ` Hannes Frederic Sowa
2015-11-17 14:46 Stefan Priebe - Profihost AG
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=1447882827.575319.443677441.6F45D05F@webmail.messagingengine.com \
--to=hannes@stressinduktion.org \
--cc=fweimer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).