From: Stefano Brivio <sbrivio@redhat.com>
To: Antoine Tenart <atenart@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, echaudro@redhat.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: do not modify the shared tunnel info when PMTU triggers an ICMP reply
Date: Thu, 25 Mar 2021 21:28:14 +0100 [thread overview]
Message-ID: <20210325212806.1ae8fec5@elisabeth> (raw)
In-Reply-To: <20210325153533.770125-1-atenart@kernel.org>
On Thu, 25 Mar 2021 16:35:31 +0100
Antoine Tenart <atenart@kernel.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@redhat.com>
Thanks for fixing this!
--
Stefano
next prev parent reply other threads:[~2021-03-25 20:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 15:35 [PATCH net 0/2] net: do not modify the shared tunnel info when PMTU triggers an ICMP reply Antoine Tenart
2021-03-25 15:35 ` [PATCH net 1/2] vxlan: " Antoine Tenart
2022-01-20 7:38 ` Vlad Buslov
2022-01-20 10:27 ` Antoine Tenart
2022-01-20 12:58 ` Vlad Buslov
2022-01-28 17:01 ` Antoine Tenart
2022-01-31 11:26 ` Vlad Buslov
2022-01-31 13:26 ` Antoine Tenart
2022-01-31 14:04 ` Stefano Brivio
2022-01-31 14:42 ` Antoine Tenart
2022-01-31 17:55 ` Vlad Buslov
2021-03-25 15:35 ` [PATCH net 2/2] geneve: " Antoine Tenart
2021-03-25 20:28 ` Stefano Brivio [this message]
2021-03-26 0:40 ` [PATCH net 0/2] net: " patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210325212806.1ae8fec5@elisabeth \
--to=sbrivio@redhat.com \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=echaudro@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.