[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1486042812.13103.27.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Thu, 02 Feb 2017 05:40:12 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Eric Dumazet <edumazet@...gle.com>,
Andrey Konovalov <andreyknvl@...gle.com>,
"David S. Miller" <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
James Morris <jmorris@...ei.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>,
netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Kostya Serebryany <kcc@...gle.com>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: net/tcp: warning in tcp_try_coalesce/skb_try_coalesce
On Thu, 2017-02-02 at 13:59 +0100, Dmitry Vyukov wrote:
>
> Right, I can confirm that this is not happening on net-next tip
> (62e13097c46c69dbd7544ab2cd585ccf48f360a4).
> I reproduced it on a random month old commit on net-next, though
> (23a8ed4a624324dc696c328f09bd502c4a3816f0). Let's consider that this
> is accidentally fixed by something in that range.
This also might depend on the .config
I tried 23a8ed4a624324dc696c328f09bd502c4a3816f0 and could not trigger
the warning .
Thanks.
Powered by blists - more mailing lists