public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <nikolay@nvidia.com>
To: Hans Schultz <schultz.hans@gmail.com>, <davem@davemloft.net>,
	<kuba@kernel.org>
Cc: <netdev@vger.kernel.org>,
	Hans Schultz <schultz.hans+netdev@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Vladimir Oltean <olteanv@gmail.com>,
	Roopa Prabhu <roopa@nvidia.com>, Shuah Khan <shuah@kernel.org>,
	"Stephen Suryaputra" <ssuryaextr@gmail.com>,
	David Ahern <dsahern@kernel.org>,
	"Ido Schimmel" <idosch@nvidia.com>,
	Petr Machata <petrm@nvidia.com>, Amit Cohen <amcohen@nvidia.com>,
	Po-Hsu Lin <po-hsu.lin@canonical.com>,
	Baowen Zheng <baowen.zheng@corigine.com>,
	<linux-kernel@vger.kernel.org>,
	<bridge@lists.linux-foundation.org>,
	<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH net-next v3 5/5] selftests: forwarding: tests of locked port feature
Date: Sat, 19 Feb 2022 11:48:59 +0200	[thread overview]
Message-ID: <9ffcbd18-bc50-cc82-3582-83b1f10e31b6@nvidia.com> (raw)
In-Reply-To: <20220218155148.2329797-6-schultz.hans+netdev@gmail.com>

On 18/02/2022 17:51, Hans Schultz wrote:
> These tests check that the basic locked port feature works, so that no 'host'
> can communicate (ping) through a locked port unless the MAC address of the
> 'host' interface is in the forwarding database of the bridge.
> 
> Signed-off-by: Hans Schultz <schultz.hans+netdev@gmail.com>
> ---
>  .../testing/selftests/net/forwarding/Makefile |   1 +
>  .../net/forwarding/bridge_locked_port.sh      | 174 ++++++++++++++++++
>  tools/testing/selftests/net/forwarding/lib.sh |  16 ++
>  3 files changed, 191 insertions(+)
>  create mode 100755 tools/testing/selftests/net/forwarding/bridge_locked_port.sh
> 
> diff --git a/tools/testing/selftests/net/forwarding/Makefile b/tools/testing/selftests/net/forwarding/Makefile
> index 72ee644d47bf..8fa97ae9af9e 100644
> --- a/tools/testing/selftests/net/forwarding/Makefile
> +++ b/tools/testing/selftests/net/forwarding/Makefile
> @@ -1,6 +1,7 @@
>  # SPDX-License-Identifier: GPL-2.0+ OR MIT
>  
>  TEST_PROGS = bridge_igmp.sh \
> +	bridge_locked_port.sh \
>  	bridge_port_isolation.sh \
>  	bridge_sticky_fdb.sh \
>  	bridge_vlan_aware.sh \
> diff --git a/tools/testing/selftests/net/forwarding/bridge_locked_port.sh b/tools/testing/selftests/net/forwarding/bridge_locked_port.sh
> new file mode 100755
> index 000000000000..d2805441b325
> --- /dev/null
> +++ b/tools/testing/selftests/net/forwarding/bridge_locked_port.sh
> @@ -0,0 +1,174 @@
> +#!/bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +
> +ALL_TESTS="locked_port_ipv4 locked_port_ipv6 locked_port_vlan"
> +NUM_NETIFS=4
> +CHECK_TC="no"
> +source lib.sh
> +
> +h1_create()
> +{
> +	simple_if_init $h1 192.0.2.1/24 2001:db8:1::1/64
> +	vrf_create "vrf-vlan-h1"
> +        ip link set dev vrf-vlan-h1 up
> +        vlan_create $h1 100 vrf-vlan-h1 192.0.3.1/24 2001:db8:3::1/64
> +}

Please use tabs similar to everywhere else in the file.


  parent reply	other threads:[~2022-02-19  9:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 15:51 [PATCH net-next v3 0/5] Add support for locked bridge ports (for 802.1X) Hans Schultz
2022-02-18 15:51 ` [PATCH net-next v3 1/5] net: bridge: Add support for bridge port in locked mode Hans Schultz
2022-02-19  9:46   ` Nikolay Aleksandrov
2022-02-20  9:18   ` Ido Schimmel
2022-02-18 15:51 ` [PATCH net-next v3 2/5] net: bridge: Add support for offloading of locked port flag Hans Schultz
2022-02-19  9:47   ` Nikolay Aleksandrov
2022-02-20  9:19   ` Ido Schimmel
2022-02-18 15:51 ` [PATCH net-next v3 3/5] net: dsa: Add support for offloaded " Hans Schultz
2022-02-19  9:56   ` Vladimir Oltean
2022-02-18 15:51 ` [PATCH net-next v3 4/5] net: dsa: mv88e6xxx: Add support for bridge port locked mode Hans Schultz
2022-02-19 10:00   ` Vladimir Oltean
2022-02-20  9:21     ` Ido Schimmel
2022-02-21 14:05       ` Hans Schultz
2022-02-18 15:51 ` [PATCH net-next v3 5/5] selftests: forwarding: tests of locked port feature Hans Schultz
2022-02-18 21:02   ` Shuah Khan
2022-02-19  9:48   ` Nikolay Aleksandrov [this message]
2022-02-20  9:12   ` Ido Schimmel
2022-02-21  9:20     ` Hans Schultz

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=9ffcbd18-bc50-cc82-3582-83b1f10e31b6@nvidia.com \
    --to=nikolay@nvidia.com \
    --cc=amcohen@nvidia.com \
    --cc=andrew@lunn.ch \
    --cc=baowen.zheng@corigine.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=petrm@nvidia.com \
    --cc=po-hsu.lin@canonical.com \
    --cc=roopa@nvidia.com \
    --cc=schultz.hans+netdev@gmail.com \
    --cc=schultz.hans@gmail.com \
    --cc=shuah@kernel.org \
    --cc=ssuryaextr@gmail.com \
    --cc=vivien.didelot@gmail.com \
    /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