[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Feb 2017 14:56:21 +0100
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Eric Dumazet <eric.dumazet@...il.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, Feb 2, 2017 at 2:40 PM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> 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 .
I've attached my config.
But I've tried with the same config on both revisions.
Well, there is also a chance that the bug is not fixed, but requires
slightly different reproducer after some changes.
Download attachment ".config" of type "application/octet-stream" (116341 bytes)
Powered by blists - more mailing lists