On Thu, 2015-06-11 at 23:03 +0100, David Woodhouse wrote:
On Thu, 2015-06-11 at 01:31 +0100, David Woodhouse wrote:
On Tue, 2015-06-09 at 17:49 -0700, Eric Dumazet wrote:
I've added some debugging, and it seems that when it deadlocks,
glibc
doesn't get *any* response to its
On Thu, 2015-06-11 at 01:31 +0100, David Woodhouse wrote:
On Tue, 2015-06-09 at 17:49 -0700, Eric Dumazet wrote:
I've added some debugging, and it seems that when it deadlocks, glibc
doesn't get *any* response to its RTM_GETADDR request. I know we'd get
ENOBUFS is a *response* was
From: David Woodhouse dw...@infradead.org
Date: Thu, 11 Jun 2015 01:31:28 +0100
On Tue, 2015-06-09 at 17:49 -0700, Eric Dumazet wrote:
I've added some debugging, and it seems that when it deadlocks, glibc
doesn't get *any* response to its RTM_GETADDR request. I know we'd get
ENOBUFS is a
On Tue, 2015-06-09 at 17:49 -0700, Eric Dumazet wrote:
I've added some debugging, and it seems that when it deadlocks, glibc
doesn't get *any* response to its RTM_GETADDR request. I know we'd get
ENOBUFS is a *response* was dropped... but what about when the request
itself is dropped? ...
On Tue, 2015-06-09 at 14:34 +0100, David Woodhouse wrote:
On Wed, 2015-04-08 at 15:08 +0200, Johannes Berg wrote:
On Wed, 2015-04-08 at 13:03 +0100, David Woodhouse wrote:
I'm not sure if this is entirely fixed. In Fedora 22 (4.0.0-rc5-git4)
I'm occasionally seeing glibc deadlock in
On Wed, 2015-04-08 at 15:08 +0200, Johannes Berg wrote:
On Wed, 2015-04-08 at 13:03 +0100, David Woodhouse wrote:
I'm not sure if this is entirely fixed. In Fedora 22 (4.0.0-rc5-git4)
I'm occasionally seeing glibc deadlock in __check_pf() on a netlink
recvmsg(), here:
On Wed, 2015-04-08 at 15:12 +0100, David Woodhouse wrote:
On Wed, 2015-04-08 at 15:08 +0200, Johannes Berg wrote:
Additionally, the failure mode of this was the process running out of
memory due to receiving the same results over and over again - does that
happen for you? It seems it was
