From: Grant Zhang <gzhang@fastly.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Patrick Schaaf <kernelorg@bof.de>,
NETDEV <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 4.1 hang, apparently in __inet_lookup_established
Date: Mon, 16 Nov 2015 09:30:07 -0800 [thread overview]
Message-ID: <564A129F.5060705@fastly.com> (raw)
In-Reply-To: <1447686469.22599.67.camel@edumazet-glaptop2.roam.corp.google.com>
On 16/11/2015 07:07, Eric Dumazet wrote:
> On Sun, 2015-11-15 at 16:58 -0800, Grant Zhang wrote:
>> Hi Patrick,
>>
>> Have you tried the two patches Eric mentioned? One of my 4.1.11 server
>> just hanged with very similar stack trace and I am wondering whether the
>> aforementioned patches would help.
>>
>> Thanks,
>
> linux-4.1.12 definitely contains the fixes.
>
> 8ae3dfacdd82 inet: fix race in reqsk_queue_unlink()
> 31b8abd140ad inet: fix races in reqsk_queue_hash_req()
>
> Please upgrade to 4.1.13 and you should be fine.
>
> Thanks.
>
>
Thank you Eric and Patrick. I will upgrade to 4.1.13.
Grant
next prev parent reply other threads:[~2015-11-16 17:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 8:25 Kernel 4.1 hang, apparently in __inet_lookup_established Patrick Schaaf
2015-09-23 16:31 ` Eric Dumazet
2015-11-16 0:58 ` Grant Zhang
2015-11-16 11:30 ` Patrick Schaaf
2015-11-16 15:07 ` Eric Dumazet
2015-11-16 17:30 ` Grant Zhang [this message]
2016-01-11 20:27 ` Grant Zhang
2016-01-11 21:11 ` Eric Dumazet
2016-01-11 21:47 ` Eric Dumazet
2016-01-13 16:01 ` David Miller
2016-01-13 16:19 ` Eric Dumazet
2016-01-13 19:38 ` David Miller
2016-01-13 22:16 ` 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=564A129F.5060705@fastly.com \
--to=gzhang@fastly.com \
--cc=eric.dumazet@gmail.com \
--cc=kernelorg@bof.de \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).