From: Jakub Kicinski <kuba@kernel.org>
To: Antoine Tenart <atenart@kernel.org>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
steffen.klassert@secunet.com, willemdebruijn.kernel@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net v3 0/4] gro: various fixes related to UDP tunnels
Date: Fri, 22 Mar 2024 15:55:50 -0700 [thread overview]
Message-ID: <20240322155550.3779c85a@kernel.org> (raw)
In-Reply-To: <20240322114624.160306-1-atenart@kernel.org>
On Fri, 22 Mar 2024 12:46:19 +0100 Antoine Tenart wrote:
> We found issues when a UDP tunnel endpoint is in a different netns than
> where UDP GRO happens. This kind of setup is actually quite diverse,
> from having one leg of the tunnel on a remove host, to having a tunnel
> between netns (eg. being bridged in another one or on the host). In our
> case that UDP tunnel was geneve.
I think this series makes net/udpgro_fwd.sh selftest fail.
next prev parent reply other threads:[~2024-03-22 22:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 11:46 [PATCH net v3 0/4] gro: various fixes related to UDP tunnels Antoine Tenart
2024-03-22 11:46 ` [PATCH net v3 1/4] udp: do not accept non-tunnel GSO skbs landing in a tunnel Antoine Tenart
2024-03-22 11:46 ` [PATCH net v3 2/4] gro: fix ownership transfer Antoine Tenart
2024-03-22 11:46 ` [PATCH net v3 3/4] udp: do not transition UDP GRO fraglist partial checksums to unnecessary Antoine Tenart
2024-03-22 17:29 ` Willem de Bruijn
2024-03-25 10:37 ` Antoine Tenart
2024-03-25 18:39 ` Willem de Bruijn
2024-03-26 9:44 ` Antoine Tenart
2024-03-26 13:37 ` Willem de Bruijn
2024-03-22 11:46 ` [PATCH net v3 4/4] udp: prevent local UDP tunnel packets from being GROed Antoine Tenart
2024-03-22 22:55 ` Jakub Kicinski [this message]
2024-03-25 10:16 ` [PATCH net v3 0/4] gro: various fixes related to UDP tunnels Antoine Tenart
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=20240322155550.3779c85a@kernel.org \
--to=kuba@kernel.org \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=willemdebruijn.kernel@gmail.com \
/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.