[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iKzeTKuBA3NL0DQUmUHmmc0QzZ0X62DUarZ2Q7cKRZvSA@mail.gmail.com>
Date: Tue, 26 Mar 2024 15:14:55 +0100
From: Eric Dumazet <edumazet@...gle.com>
To: Richard Gobert <richardbgobert@...il.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
willemdebruijn.kernel@...il.com, dsahern@...nel.org, xeb@...l.ru,
shuah@...nel.org, idosch@...dia.com, amcohen@...dia.com, petrm@...dia.com,
jbenc@...hat.com, bpoirier@...dia.com, b.galvani@...il.com,
liujian56@...wei.com, horms@...nel.org, linyunsheng@...wei.com,
therbert@...gle.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH net-next v4 4/4] net: gro: move L3 flush checks to tcp_gro_receive
On Mon, Mar 25, 2024 at 7:27 PM Richard Gobert <richardbgobert@...il.com> wrote:
>
> {inet,ipv6}_gro_receive functions perform flush checks (ttl, flags,
> iph->id, ...) against all packets in a loop. These flush checks are used
> currently only in tcp flows in GRO.
I think this is a bug.
GRO should not aggregate packets if their ttl/tos fields do not match.
Powered by blists - more mailing lists