[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CANn89iJ1JVG_H-FAQRg3JdPtNkq2T++K9Xc-mLo_VaUdcp38KA@mail.gmail.com>
Date: Thu, 27 Oct 2022 05:04:54 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: "luwei (O)" <luwei32@...wei.com>
Cc: Pavel Emelyanov <ovzxemul@...il.com>,
"Denis V. Lunev" <den@...tuozzo.com>, davem@...emloft.net,
yoshfuji@...ux-ipv6.org, dsahern@...nel.org, kuba@...nel.org,
pabeni@...hat.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, avagin@...il.com,
Pavel Tikhomirov <ptikhomirov@...tuozzo.com>
Subject: Re: [PATCH net] tcp: reset tp->sacked_out when sack is enabled
On Thu, Oct 27, 2022 at 5:00 AM luwei (O) <luwei32@...wei.com> wrote:
>
>
> thanks, I will send next version
Yeah, what about first agreeing on what the plans are ?
In order to avoid confusion and lkml/netdev bloat, I think you should
describe why existing checks are not enough.
Since this was probably caught by a fuzzer like syzbot, do you have a repro ?
Powered by blists - more mailing lists