Netdev List
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Minxi Hou <houminxi@gmail.com>, netdev@vger.kernel.org
Cc: aconole@redhat.com, davem@davemloft.net, dev@openvswitch.org,
	echaudro@redhat.com, edumazet@google.com, i.maximets@ovn.org,
	i.maximets@redhat.com, kuba@kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	shuah@kernel.org, horms@kernel.org
Subject: Re: [PATCH net-next 0/2] selftests: openvswitch: SCTP flow key coverage (IPv6 + NAT)
Date: Tue, 25 Aug 2026 11:51:47 +0200	[thread overview]
Message-ID: <e94063e0-bea4-4fee-b4b0-2934b3bb66a0@redhat.com> (raw)
In-Reply-To: <20260823020942.3101898-1-houminxi@gmail.com>

On 8/23/26 4:09 AM, Minxi Hou wrote:
> The SCTP flow key test merged last week covers only IPv4 and only the
> plain forwarding path. This series extends coverage to the two paths a
> regression would otherwise ship silently on: SCTP over IPv6, and SCTP
> across conntrack NAT (where OVS re-extracts L3/L4 on the recirculated
> skb).
> 
> Both tests verify the association and then push a known payload across
> and confirm the listener received it, so a flow-key bug that matches
> handshake packets but breaks DATA chunks is caught rather than passing
> on the handshake alone.
> 
> Full OVS selftest suite runs 19/19 green on a freshly built kernel.
> 
> Minxi Hou (2):
>   selftests/net/openvswitch: add SCTP flow key test over IPv6
>   selftests/net/openvswitch: add SCTP flow key test across conntrack NAT
> 
>  .../selftests/net/openvswitch/openvswitch.sh  | 183 +++++++++++++++++-
>  1 file changed, 182 insertions(+), 1 deletion(-)
> 
> 
> base-commit: 91ec2035134982b98fab0609a9fd8480e8217dc1

## Form letter - net-next-closed

net-next pull request for v7.3 has already been merged, and therefore
the net-next tree is closed for new drivers, features, code refactoring
and optimizations. We are currently accepting bug fixes only.

Please repost when net-next reopens after Aug 31st.

RFC patches sent for review only are obviously welcome at any time.

See:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
-- 
pw-bot: defer
pv-bot: closed




      parent reply	other threads:[~2026-08-25  9:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23  2:09 [PATCH net-next 0/2] selftests: openvswitch: SCTP flow key coverage (IPv6 + NAT) Minxi Hou
2026-08-23  2:09 ` [PATCH net-next 1/2] selftests/net/openvswitch: add SCTP flow key test over IPv6 Minxi Hou
2026-08-23  2:09 ` [PATCH net-next 2/2] selftests/net/openvswitch: add SCTP flow key test across conntrack NAT Minxi Hou
2026-08-25  9:51 ` Paolo Abeni [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=e94063e0-bea4-4fee-b4b0-2934b3bb66a0@redhat.com \
    --to=pabeni@redhat.com \
    --cc=aconole@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=echaudro@redhat.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=houminxi@gmail.com \
    --cc=i.maximets@ovn.org \
    --cc=i.maximets@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox