From: Guenter Roeck <linux@roeck-us.net>
To: Steven Schlansker <stevenschlansker@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org
Subject: Re: Glibc recvmsg from kernel netlink socket hangs forever
Date: Mon, 5 Oct 2015 16:30:25 -0700 [thread overview]
Message-ID: <56130811.8080902@roeck-us.net> (raw)
In-Reply-To: <368A90AB-8181-4C13-B5EA-B9378CA4C71B@gmail.com>
On 10/05/2015 04:26 PM, Steven Schlansker wrote:
>
> On Sep 25, 2015, at 7:58 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>
>> On 09/25/2015 02:37 PM, Steven Schlansker wrote:
>>>
>>>
>>> Thank you for the patches to try, I'll build a kernel with them early next week
>>> and report back. It sounds like it may not match my problem exactly so we'll
>>> see.
>>>
>>
>> For 4.0.x, you _really_ need to update to 4.0.9 to get the following two patches.
>>
>> cf8befcc1a55 netlink: Disable insertions/removals during rehash
>> 18889a4315a5 netlink: Reset portid after netlink_insert failure
>
> Hi Guenter,
>
> Thank you very much for the information. We upgraded to 4.0.9 and all indications are that
> the issue is gone. I will follow up if that is not the case.
>
> Thank you everyone for your guidance.
>
My pleasure.
Guenter
next prev parent reply other threads:[~2015-10-05 23:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 0:29 Glibc recvmsg from kernel netlink socket hangs forever Steven Schlansker
2015-09-25 4:36 ` Guenter Roeck
2015-09-25 4:58 ` Herbert Xu
2015-09-25 5:34 ` Guenter Roeck
2015-09-25 15:55 ` Herbert Xu
2015-09-25 16:14 ` Guenter Roeck
2015-09-26 3:45 ` Guenter Roeck
2015-09-25 21:37 ` Steven Schlansker
2015-09-25 21:54 ` Steven Schlansker
2015-09-26 2:58 ` Guenter Roeck
2015-10-05 23:26 ` Steven Schlansker
2015-10-05 23:30 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-11 19:33 Jun Wang
2016-03-11 23:50 ` Guenter Roeck
2016-03-12 0:13 ` Cong Wang
2016-03-12 1:25 ` Guenter Roeck
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=56130811.8080902@roeck-us.net \
--to=linux@roeck-us.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stevenschlansker@gmail.com \
/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.