netdev - Re: [PATCH v3 net-next 0/5] selftests: openvswitch: add flow programming cases

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8470c431e0930d2ea204a9363a60937289b7fdbe.camel@redhat.com>
Date: Thu, 03 Aug 2023 15:22:12 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Aaron Conole <aconole@...hat.com>, netdev@...r.kernel.org
Cc: dev@...nvswitch.org, linux-kselftest@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Shuah Khan <shuah@...nel.org>, Jakub Kicinski
	 <kuba@...nel.org>, Eric Dumazet <edumazet@...gle.com>, "David S. Miller"
	 <davem@...emloft.net>, Pravin B Shelar <pshelar@....org>, Adrian Moreno
	 <amorenoz@...hat.com>, Ilya Maximets <i.maximets@....org>
Subject: Re: [PATCH v3 net-next 0/5] selftests: openvswitch: add flow
 programming cases

On Tue, 2023-08-01 at 17:22 -0400, Aaron Conole wrote:
> The openvswitch selftests currently contain a few cases for managing the
> datapath, which includes creating datapath instances, adding interfaces,
> and doing some basic feature / upcall tests.  This is useful to validate
> the control path.
> 
> Add the ability to program some of the more common flows with actions. This
> can be improved overtime to include regression testing, etc.
> 
> v2->v3:
> 1. Dropped support for ipv6 in nat() case
> 2. Fixed a spelling mistake in 2/5 commit message.
> 
> v1->v2:
> 1. Fix issue when parsing ipv6 in the NAT action
> 2. Fix issue calculating length during ctact parsing
> 3. Fix error message when invalid bridge is passed
> 4. Fold in Adrian's patch to support key masks

FTR, this apparently requires an [un?]fairly recent version of
pyroute2. Perhaps you could explicitly check for a minimum working
version and otherwise bail out (skip) the add-flow tests.

Cheers,

Paolo