All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: "Eva Kurchatova (Virtuozzo)" <eva.kurchatova@virtuozzo.com>
To: devel@openvz.org, Konstantin Khorenko <khorenko@virtuozzo.com>
Subject: Re: [Devel] [PATCH hci-8.1 v4 0/1] selftests: net: skip the veth GRO checks where they cannot run
Date: Tue, 27 Oct 2026 19:44:30 +0200	[thread overview]
Message-ID: <f76d64c7-1d9c-4a08-8f1d-7c8e86104575@virtuozzo.com> (raw)
In-Reply-To: <20261005112332.1989594-1-eva.kurchatova@virtuozzo.com>


On 10/5/26 14:23, Eva Kurchatova wrote:
> Patchset for task https://virtuozzo.atlassian.net/browse/VSTOR-139651
>
> Changes in v4:
> - Fix the test in chk_gro_fwd(): it skipped on a clean host and ran
>    with a tunnel, udp_encap_in_use() returns 0 when it finds one.
> - Rebased.
>
> Link to v3: http://lore.virtuozzo.com/kernel/20260928193506.549055-1-eva.kurchatova@virtuozzo.com/T/#t
>
> Changes in v3:
> - Skip the three forwarding checks when UDP encapsulation is in use on
>    the host, instead of asking for UDP GRO on the receiver, which made
>    them pass without testing rx-udp-gro-forwarding.
> - Drop the comment, the reason is in the message.
> - Retitled. Sent alone, the rest of v2 is merged.
>
> Link to v2: https://lists.openvz.org/pipermail/devel/2026-September/085192.html
>
> Changes in v2:
> - Unchanged, renumbered within the series.
>
> Link to v1: https://lists.openvz.org/pipermail/devel/2026-September/084951.html
>
> Eva Kurchatova (1):
>    selftests: net: skip the veth GRO checks where they cannot run
>
>   tools/testing/selftests/net/veth.sh | 47 +++++++++++++++++++++++++++--
>   1 file changed, 44 insertions(+), 3 deletions(-)

This patch is obsoleted by the "selftests: net: veth: run under separate 
netns" series at 
http://lore.virtuozzo.com/kernel/20261027-b4-prep-khorenko-vstor-151678-veth-udp-gro-fwd-v2-0-33d8d5c1f257@virtuozzo.com/T/#t

Drop it: It was based on my older investigation that concluded that UDP 
GRO may not run with active tunnels at all. That turned out to be 
incorrect, and would cost coverage for this subtest run.

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

      parent reply	other threads:[~2026-10-27 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 11:23 Eva Kurchatova
2026-10-05 11:23 ` [Devel] [PATCH hci-8.1 v4 1/1] " Eva Kurchatova
2026-10-05 11:29   ` no-reply
2026-10-27 17:44 ` Eva Kurchatova (Virtuozzo) [this message]

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=f76d64c7-1d9c-4a08-8f1d-7c8e86104575@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 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.