netdev - Re: [PATCH net 0/2] net: do not modify the shared tunnel info when PMTU triggers an ICMP reply

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 25 Mar 2021 21:28:14 +0100
From:   Stefano Brivio <sbrivio@...hat.com>
To:     Antoine Tenart <atenart@...nel.org>
Cc:     davem@...emloft.net, kuba@...nel.org, echaudro@...hat.com,
        netdev@...r.kernel.org
Subject: Re: [PATCH net 0/2] net: do not modify the shared tunnel info when
 PMTU triggers an ICMP reply

On Thu, 25 Mar 2021 16:35:31 +0100
Antoine Tenart <atenart@...nel.org> wrote:

> Hi,
> 
> The series fixes an issue were a shared ip_tunnel_info is modified when
> PMTU triggers an ICMP reply in vxlan and geneve, making following
> packets in that flow to have a wrong destination address if the flow
> isn't updated. A detailled information is given in each of the two
> commits.
> 
> This was tested manually with OVS and I ran the PTMU selftests with
> kmemleak enabled (all OK, none was skipped).
> 
> Thanks!
> Antoine
> 
> Antoine Tenart (2):
>   vxlan: do not modify the shared tunnel info when PMTU triggers an ICMP
>     reply
>   geneve: do not modify the shared tunnel info when PMTU triggers an
>     ICMP reply

For the series,

Reviewed-by: Stefano Brivio <sbrivio@...hat.com>

Thanks for fixing this!

-- 
Stefano