All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: jpeska <jpeska@redhat.com>
Cc: netfilter-devel@vger.kernel.org, fwestpha@redhat.com
Subject: Re: [PATCH nf-next] selftests: netfilter: add UDP flowtable offload test
Date: Wed, 11 Nov 2026 00:51:59 +0100	[thread overview]
Message-ID: <avOuH_ayOgr5x6DJ@strlen.de> (raw)
In-Reply-To: <20261109135137.1770507-1-jpeska@redhat.com>

jpeska <jpeska@redhat.com> wrote:
> nft_flowtable.sh offloads only TCP, so the UDP flowtable paths never
> run: the UDP tuple lookup, the UDP checksum update, IPv6 source NAT,
> and nf_ct_acct_update behind the flowtable counter flag.
> 
> Add an echo test for IPv4 and IPv6, with and without masquerade. The
> payload must come back intact, the forward chain must see only the
> handshake, and conntrack must mark the flow OFFLOAD and account every
> datagram.

In case you did not see it yet:

https://sashiko.dev/#/patchset/20261109135137.1770507-1-jpeska%40redhat.com

Wrt. the various CONFIG_* comments:

The kfselftests CAN assume that the kernel has the options defined
in selftests/net/netfilter/config , so there is no need to go above and
beyond and tolerate all kinds of stuff being absent.

exit $ksft_skip instead of exit 1 when its clearly a missing
config option is fine, but if its not easy to tell why something
is failing (e.g. nft -f foo.txt when run on kernel that lacks a
particular nftables module but that module is listed in the config
file -- exit 1, no need to start guessing.

$ksft_skip is only ok if there is no doubt whatsoever that the
failure is because of a missing option/feature.

Wrt to NETIF_F_HW_CSUM comment, I think one could start playing
with ethtool and the checksum features (ethtool -k) to check
different combinations.

Might make sense to integrate this script with nft_flowtable.sh
so that tcp can be easily covered too.  Also nft_flowtable.sh
re-runs itself with random mtu sizes, this is also helpful to spot
any MTU (defrag/refrag) problems.

But up to you.

      parent reply	other threads:[~2026-11-10 23:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 13:51 [PATCH nf-next] selftests: netfilter: add UDP flowtable offload test jpeska
2026-11-09 15:45 ` Florian Westphal
2026-11-10 23:51 ` Florian Westphal [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=avOuH_ayOgr5x6DJ@strlen.de \
    --to=fw@strlen.de \
    --cc=fwestpha@redhat.com \
    --cc=jpeska@redhat.com \
    --cc=netfilter-devel@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.