From: Aaron Conole <aconole@redhat.com>
To: houminxi@gmail.com
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, echaudro@redhat.com,
i.maximets@ovn.org, i.maximets@redhat.com, dev@openvswitch.org,
linux-kselftest@vger.kernel.org, shuah@kernel.org,
horms@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next,v6,1/2] selftests/net/openvswitch: add SCTP flow key parsing to ovs-dpctl.py
Date: Fri, 24 Jul 2026 15:02:01 -0400 [thread overview]
Message-ID: <f7th5loxlcm.fsf@redhat.com> (raw)
In-Reply-To: <20260724150624.3457427-2-houminxi@gmail.com>
Minxi Hou <houminxi@gmail.com> writes:
> The ovskey flow-string parser has no OVS_KEY_ATTR_SCTP entry, so a
> flow string containing sctp(src=.../dst=...) parses without error but
> silently drops the L4 key. The resulting flow carries only
> ipv4(proto=132), and the kernel rejects it: match_validate() in
> flow_netlink.c requires OVS_KEY_ATTR_SCTP when the IP protocol is
> IPPROTO_SCTP and returns -EINVAL for the missing key.
>
> Register OVS_KEY_ATTR_SCTP in the parse table and add unit tests
> (runnable via ovs-dpctl.py --test) covering SCTP and the neighboring
> TCP/UDP/ICMP/IPv4 key parsers.
>
> Signed-off-by: Minxi Hou <houminxi@gmail.com>
> ---
> .../selftests/net/openvswitch/ovs-dpctl.py | 129 ++++++++++++++++++
> 1 file changed, 129 insertions(+)
[...]
> @@ -3165,5 +3171,128 @@ def main(argv):
> return 0
>
>
> +def _init_ovskey_nlas():
> + """Initialize required NLA classes for ovskey parsing."""
> + nlmsg_atoms.encap_ovskey = encap_ovskey
> + nlmsg_atoms.ovskey = ovskey
> + nlmsg_atoms.ovsactions = ovsactions
> +
> +
> +def _parse_flow(flowstr):
> + """Parse a flow string and return the key."""
> + key = ovskey()
> + key["attrs"] = []
> + key.parse(flowstr)
> + return key
> +
> +
> +def _find_attr(key, attr_name):
> + """Find an attribute in parsed key."""
> + for attr in key["attrs"]:
> + if attr[0] == attr_name:
> + return attr[1]
> + return None
> +
> +
> +class TestOvsKeyParse(unittest.TestCase):
> + """Unit tests for ovskey.parse() flow string parsing."""
[...]
I don't think we need unit tests for the unit test... That seems like
extra working making tests all the way down.
Maybe someone disagrees, but to me a test case here feels a bit
excessive.
next prev parent reply other threads:[~2026-07-24 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 15:06 [PATCH net-next v6 0/2] selftests/net/openvswitch: add SCTP flow key test Minxi Hou
2026-07-24 15:06 ` [PATCH net-next v6 1/2] selftests/net/openvswitch: add SCTP flow key parsing to ovs-dpctl.py Minxi Hou
2026-07-24 19:02 ` Aaron Conole [this message]
2026-07-24 15:06 ` [PATCH net-next v6 2/2] selftests/net/openvswitch: add SCTP flow key test Minxi Hou
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=f7th5loxlcm.fsf@redhat.com \
--to=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=pabeni@redhat.com \
--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