From: David Woodhouse <dwmw2@infradead•org>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: Johannes Berg <johannes@sipsolutions•net>,
David Miller <davem@davemloft•net>,
torvalds@linux-foundation•org, marcel@holtmann•org,
sfeldma@gmail•com, netdev@vger•kernel.org, teg@jklm•no
Subject: Re: Problem with patch "make nlmsg_end() and genlmsg_end() void"
Date: Thu, 11 Jun 2015 23:03:55 +0100 [thread overview]
Message-ID: <1434060235.14843.2.camel@infradead.org> (raw)
In-Reply-To: <1433982688.3907.7.camel@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
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 dropped... but what about when the request
> > > itself is dropped? ...
> >
> > Please check that this patch fixes your issue :
> >
> > http://patchwork.ozlabs.org/patch/473041/
>
> Looks likely; thanks. I'm running with that patch now. I haven't been
> able to quickly reproduce the problem on demand, but it usually happens
> within a day or two. So it'll be a few days at least before I call it a
> success.
I just saw the same deadlock happen again; glibc's __check_pf() stuck
in recvmsg() waiting for a response that never comes.
This is the Fedora 22 4.0.5 kernel with the above patch applied.
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]
next prev parent reply other threads:[~2015-06-11 22:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 11:44 Problem with patch "make nlmsg_end() and genlmsg_end() void" Marcel Holtmann
2015-01-18 23:44 ` Marcel Holtmann
2015-01-19 1:53 ` Scott Feldman
2015-01-19 2:10 ` Marcel Holtmann
2015-01-19 4:37 ` David Miller
2015-01-19 9:31 ` Scott Feldman
2015-04-08 12:03 ` David Woodhouse
2015-04-08 13:08 ` Johannes Berg
2015-04-08 14:12 ` David Woodhouse
2015-04-20 14:30 ` David Woodhouse
2015-06-09 13:34 ` David Woodhouse
2015-06-10 0:49 ` Eric Dumazet
2015-06-11 0:31 ` David Woodhouse
2015-06-11 7:16 ` David Miller
2015-06-11 22:03 ` David Woodhouse [this message]
2015-06-18 6:38 ` David Woodhouse
2015-01-19 8:53 ` Johannes Berg
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=1434060235.14843.2.camel@infradead.org \
--to=dwmw2@infradead$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=johannes@sipsolutions$(echo .)net \
--cc=marcel@holtmann$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfeldma@gmail$(echo .)com \
--cc=teg@jklm$(echo .)no \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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