From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: gzhang@fastly.com, kernelorg@bof.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Kernel 4.1 hang, apparently in __inet_lookup_established
Date: Wed, 13 Jan 2016 14:38:45 -0500 (EST) [thread overview]
Message-ID: <20160113.143845.2024795815995912436.davem@davemloft.net> (raw)
In-Reply-To: <1452701990.1223.67.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 13 Jan 2016 08:19:50 -0800
> On Wed, 2016-01-13 at 11:01 -0500, David Miller wrote:
>> From: Eric Dumazet <eric.dumazet@gmail.com>
>> Date: Mon, 11 Jan 2016 13:11:28 -0800
>>
>> > David, can you make sure ed2e923945892a8372ab70d2f61d364b0b6d9054 is
>> > pushed to stable trees (4.1 & 4.2)
>>
>> It should definitely be there:
>>
>> [davem@localhost linux-stable]$ git shortlog v4.1.. -- include/net/inet_timewait_sock.h
>> David S. Miller (1):
>> Merge git://git.kernel.org/.../davem/net
>>
>> Eric Dumazet (4):
>> inet: simplify timewait refcounting
>> inet: inet_twsk_deschedule factorization
>> tcp/dccp: fix timewait races in timer handling
>> net: align sk_refcnt on 128 bytes boundary
>>
>> Raanan Avargil (1):
>> tcp/dccp: fix old style declarations
>>
>
> Nothing yet on 4.1.15 and 4.2.8
I should really learn how to use GIT properly, thanks Eric I'll queue
the two patches up. :-)
next prev parent reply other threads:[~2016-01-13 19:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 8:25 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
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 [this message]
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=20160113.143845.2024795815995912436.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=gzhang@fastly.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
all inboxes | Powered by JetHome®