[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1509744679.2849.66.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Fri, 03 Nov 2017 14:31:19 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Oleksandr Natalenko <oleksandr@...alenko.name>
Cc: David Miller <davem@...emloft.net>,
Yuchung Cheng <ycheng@...gle.com>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Roman Gushchin <guro@...com>, netdev <netdev@...r.kernel.org>,
Neal Cardwell <ncardwell@...gle.com>,
Lawrence Brakmo <brakmo@...com>
Subject: Re: [PATCH net] tcp: fix tcp_mtu_probe() vs highest_sack
On Fri, 2017-11-03 at 19:22 +0100, Oleksandr Natalenko wrote:
> Hi.
>
> Thanks for the fix.
>
> However, tcp_fastretrans_alert() warning case still remains open even with
> this patch. Do I understand correctly that these are 2 different issues?
>
> Currently, I use latest 4.13 stable kernel + this patch and still get:
>
> WARNING: CPU: 1 PID: 736 at net/ipv4/tcp_input.c:2826 tcp_fastretrans_alert
> +0x7c8/
My patch only fixed the panics that you guys reported.
The warning issue in fastretrans is a separate problem,
we are still working on it, but at least the effects are not
catastrophic.
Powered by blists - more mailing lists