[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iJ-iMgoy9AYoAhZ3y8wcNCsQ5Bu=4rnC3x1o9UY07E9Ag@mail.gmail.com>
Date: Wed, 20 Apr 2022 19:00:01 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Francesco Ruggeri <fruggeri@...sta.com>
Cc: Paolo Abeni <pabeni@...hat.com>, Jakub Kicinski <kuba@...nel.org>,
David Ahern <dsahern@...nel.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
David Miller <davem@...emloft.net>,
LKML <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH v2 net] tcp: md5: incorrect tcp_header_len for incoming connections
On Wed, Apr 20, 2022 at 5:50 PM Francesco Ruggeri <fruggeri@...sta.com> wrote:
>
> In tcp_create_openreq_child we adjust tcp_header_len for md5 using the
> remote address in newsk. But that address is still 0 in newsk at this
> point, and it is only set later by the callers (tcp_v[46]_syn_recv_sock).
> Use the address from the request socket instead.
>
>
>
> Fixes: cfb6eeb4c860 ("[TCP]: MD5 Signature Option (RFC2385) support.")
> Signed-off-by: Francesco Ruggeri <fruggeri@...sta.com>
Thanks for fixing this Francesco.
Reviewed-by: Eric Dumazet <edumazet@...gle.com>
Powered by blists - more mailing lists