netdev - Re: net-next: WARNING: CPU: 0 PID: 1544 at net/ipv4/tcp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CANn89iJjzB=aq6kNheT++=Q3iwqyj_J2hkhX3SrYGisG1QPbZA@mail.gmail.com>
Date:   Mon, 16 Oct 2017 18:32:29 -0700
From:   Eric Dumazet <edumazet@...gle.com>
To:     Andrei Vagin <avagin@...il.com>, Yuchung Cheng <ycheng@...gle.com>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: net-next: WARNING: CPU: 0 PID: 1544 at net/ipv4/tcp_input.c:889

On Mon, Oct 16, 2017 at 4:11 PM, Andrei Vagin <avagin@...il.com> wrote:
> Hi Eric,
>
> Could you take a look at this warning? It may be related with your
> recent patches. First time we saw this warning 7 days ago
> (net-next/master) and now we see it regularly.
>
> I printed tp->fackets_out and state->reord  before the warnings and
> here are values for them:
> tp->fackets_out = -1 state->reord = 4
>
> In my case, this warning is triggered for connections which have been
> restored by CRIU.
>
> Let me know if you need any other information. I can reproduce this
> bugs for an hour.
>
> Thanks,
> Andrei

Hi Andrei

We are aware of these recurring issues and Yuchung and other Googlers
decided it was time to remove FACK.

Stay tuned.