From: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 1/1] udp: let rx-udp-gro-forwarding aggregate under encapsulation
Date: Wed, 7 Oct 2026 23:22:38 +0300 [thread overview]
Message-ID: <20261007202324.2719416-2-eva.kurchatova@virtuozzo.com> (raw)
In-Reply-To: <20261007202324.2719416-1-eva.kurchatova@virtuozzo.com>
The rx-udp-gro-forwarding checks of the veth selftest fail with "got
10 packets, expected 1" on a host where something uses UDP encap,
for example a vxlan, and pass on a host where nothing does.
Since commit f2e9de210d50 ("udp: gro behind static key") the receiving
socket is looked up only once a tunnel socket exists, and commit
36707061d6ba ("udp: allow forwarding of plain (non-fraglisted) UDP GRO
packets") takes "no socket found" for "forwarded" and aggregates only
then. So the device setting works on a host without a tunnel and stops
working with one.
Aggregate whenever the device asks, socket found or not. That is what
every host without a tunnel has done all along: a local socket without
UDP_GRO gets the packets resegmented on delivery, and a tunnel socket
keeps its own receive path.
https://virtuozzo.atlassian.net/browse/VSTOR-139651
Feature: fix ms/udp
Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
---
net/ipv4/udp_offload.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/ipv4/udp_offload.c b/net/ipv4/udp_offload.c
index 4245522d4201..375273572ecb 100644
--- a/net/ipv4/udp_offload.c
+++ b/net/ipv4/udp_offload.c
@@ -650,7 +650,7 @@ struct sk_buff *udp_gro_receive(struct list_head *head, struct sk_buff *skb,
if (skb->dev->features & NETIF_F_GRO_FRAGLIST)
NAPI_GRO_CB(skb)->is_flist = sk ? !udp_test_bit(GRO_ENABLED, sk) : 1;
- if ((!sk && (skb->dev->features & NETIF_F_GRO_UDP_FWD)) ||
+ if ((skb->dev->features & NETIF_F_GRO_UDP_FWD) ||
(sk && udp_test_bit(GRO_ENABLED, sk)) || NAPI_GRO_CB(skb)->is_flist)
return call_gro_receive(udp_gro_receive_segment, head, skb);
--
2.56.0
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-10-07 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 20:22 [Devel] [PATCH hci-8.1 0/1] " Eva Kurchatova
2026-10-07 20:22 ` Eva Kurchatova [this message]
2026-10-07 20:28 ` [Devel] [PATCH hci-8.1 1/1] " no-reply
2026-10-08 15:44 ` Konstantin Khorenko
2026-10-08 15:42 ` [Devel] [PATCH hci-8.1 0/1] " Konstantin Khorenko
2026-10-08 16:31 ` Konstantin Khorenko
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=20261007202324.2719416-2-eva.kurchatova@virtuozzo.com \
--to=eva.kurchatova@virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox