linux.git/tools/testing/selftests/net/openvswitch, branch v6.6-rc2

selftests: openvswitch: add explicit drop testcase

2023-08-14T07:01:06+00:00

Test explicit drops generate the right drop reason. Also, verify that
the kernel rejects flows with actions following an explicit drop.

Acked-by: Aaron Conole 
Signed-off-by: Adrian Moreno 
Signed-off-by: David S. Miller

selftests: openvswitch: add drop reason testcase

2023-08-14T07:01:06+00:00

Test if the correct drop reason is reported when OVS drops a packet due
to an explicit flow.

Acked-by: Aaron Conole 
Signed-off-by: Adrian Moreno 
Signed-off-by: David S. Miller

net: openvswitch: add explicit drop action

2023-08-14T07:01:06+00:00

From: Eric Garver 

This adds an explicit drop action. This is used by OVS to drop packets
for which it cannot determine what to do. An explicit action in the
kernel allows passing the reason _why_ the packet is being dropped or
zero to indicate no particular error happened (i.e: OVS intentionally
dropped the packet).

Since the error codes coming from userspace mean nothing for the kernel,
we squash all of them into only two drop reasons:
- OVS_DROP_EXPLICIT_WITH_ERROR to indicate a non-zero value was passed
- OVS_DROP_EXPLICIT to indicate a zero value was passed (no error)

e.g. trace all OVS dropped skbs

 # perf trace -e skb:kfree_skb --filter="reason >= 0x30000"
 [..]
 106.023 ping/2465 skb:kfree_skb(skbaddr: 0xffffa0e8765f2000, \
  location:0xffffffffc0d9b462, protocol: 2048, reason: 196611)

reason: 196611 --> 0x30003 (OVS_DROP_EXPLICIT)

Also, this patch allows ovs-dpctl.py to add explicit drop actions as:
  "drop"     -> implicit empty-action drop
  "drop(0)"  -> explicit non-error action drop
  "drop(42)" -> explicit error action drop

Signed-off-by: Eric Garver 
Co-developed-by: Adrian Moreno 
Signed-off-by: Adrian Moreno 
Signed-off-by: David S. Miller

selftests: openvswitch: add ct-nat test case with ipv4

2023-08-03T13:05:41+00:00

Building on the previous work, add a very simplistic NAT case
using ipv4.  This just tests dnat transformation

Signed-off-by: Aaron Conole 
Reviewed-by: Simon Horman 
Signed-off-by: Paolo Abeni

selftests: openvswitch: add basic ct test case parsing

2023-08-03T13:05:41+00:00

Forwarding via ct() action is an important use case for openvswitch, but
generally would require using a full ovs-vswitchd to get working. Add a
ct action parser for basic ct test case.

Signed-off-by: Aaron Conole 
Reviewed-by: Adrian Moreno 
Reviewed-by: Simon Horman 
Signed-off-by: Paolo Abeni

selftests: openvswitch: add a test for ipv4 forwarding

2023-08-03T13:05:41+00:00

This is a simple ipv4 bidirectional connectivity test.

Signed-off-by: Aaron Conole 
Reviewed-by: Adrian Moreno 
Reviewed-by: Simon Horman 
Signed-off-by: Paolo Abeni

selftests: openvswitch: support key masks

2023-08-03T13:05:41+00:00

The default value for the mask actually depends on the value (e.g: if
the value is non-null, the default is full-mask), so change the convert
functions to accept the full, possibly masked string and let them figure
out how to parse the different values.

Also, implement size-aware int parsing.

With this patch we can now express flows such as the following:
"eth(src=0a:ca:fe:ca:fe:0a/ff:ff:00:00:ff:00)"
"eth(src=0a:ca:fe:ca:fe:0a)" -> mask = ff:ff:ff:ff:ff:ff
"ipv4(src=192.168.1.1)" -> mask = 255.255.255.255
"ipv4(src=192.168.1.1/24)"
"ipv4(src=192.168.1.1/255.255.255.0)"
"tcp(src=8080)" -> mask = 0xffff
"tcp(src=8080/0xf0f0)"

Signed-off-by: Adrian Moreno 
Acked-by: Aaron Conole 
Reviewed-by: Simon Horman 
Signed-off-by: Paolo Abeni

selftests: openvswitch: add an initial flow programming case

2023-08-03T13:05:41+00:00

The openvswitch self-tests can test much of the control side of
the module (ie: what a vswitchd implementation would process),
but the actual packet forwarding cases aren't supported, making
the testing of limited value.

Add some flow parsing and an initial ARP based test case using
arping utility.  This lets us display flows, add some basic
output flows with simple matches, and test against a known good
forwarding case.

Signed-off-by: Aaron Conole 
Reviewed-by: Adrian Moreno 
Reviewed-by: Simon Horman 
Signed-off-by: Paolo Abeni

selftests: openvswitch: add support for upcall testing

2023-04-17T07:12:33+00:00

The upcall socket interface can be exercised now to make sure that
future feature adjustments to the field can maintain backwards
compatibility.

Signed-off-by: Aaron Conole 
Signed-off-by: David S. Miller

selftests: openvswitch: add flow dump support

2023-04-17T07:12:33+00:00

Add a basic set of fields to print in a 'dpflow' format.  This will be
used by future commits to check for flow fields after parsing, as
well as verifying the flow fields pushed into the kernel from
userspace.

Signed-off-by: Aaron Conole 
Signed-off-by: David S. Miller