[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANn89iJxMGhXPxAekxZ9tALWVb=0oRGxdR95oM9ijBHGohTSNw@mail.gmail.com>
Date: Wed, 26 Jan 2022 17:02:34 -0800
From: Eric Dumazet <edumazet@...gle.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Eric Dumazet <eric.dumazet@...il.com>,
"David S . Miller" <davem@...emloft.net>,
David Ahern <dsahern@...nel.org>,
netdev <netdev@...r.kernel.org>, Ray Che <xijiache@...il.com>,
Geoff Alexander <alexandg@...unm.edu>, Willy Tarreau <w@....eu>
Subject: Re: [PATCH net 1/2] ipv4: tcp: send zero IPID in SYNACK messages
On Wed, Jan 26, 2022 at 4:56 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Wed, 26 Jan 2022 12:05:17 -0800 Eric Dumazet wrote:
> > + /* TCP packets here are SYNACK with fat IPv4/TCP options.
> > + * Avoid using the hashed IP ident generator.
> > + */
> > + if (sk->sk_protocol == IPPROTO_TCP)
> > + iph->id = prandom_u32();
>
> Is it worth marking this as (__force __be32) to avoid the false
> positive sparse warning?
Sure thing, we can add this (I guess this needs to be __be16 ?)
Powered by blists - more mailing lists