netdev - [PATCH net-next 0/4] selftests: mlxsw: Add ordering tests for unified bridge model

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-next>] [day] [month] [year] [list]

Message-ID: <cover.1660747162.git.petrm@nvidia.com>
Date:   Wed, 17 Aug 2022 17:28:24 +0200
From:   Petr Machata <petrm@...dia.com>
To:     "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>, <netdev@...r.kernel.org>
CC:     Ido Schimmel <idosch@...dia.com>, Amit Cohen <amcohen@...dia.com>,
        "Shuah Khan" <shuah@...nel.org>, Petr Machata <petrm@...dia.com>,
        <mlxsw@...dia.com>
Subject: [PATCH net-next 0/4] selftests: mlxsw: Add ordering tests for unified bridge model

Amit Cohen writes:

Commit 798661c73672 ("Merge branch 'mlxsw-unified-bridge-conversion-part-6'")
converted mlxsw driver to use unified bridge model. In the legacy model,
when a RIF was created / destroyed, it was firmware's responsibility to
update it in the relevant FID classification records. In the unified bridge
model, this responsibility moved to software.

This set adds tests to check the order of configuration for the following
classifications:
1. {Port, VID} -> FID
2. VID -> FID
3. VNI -> FID (after decapsulation)

In addition, in the legacy model, software is responsible to update a
table which is used to determine the packet's egress VID. Add a test to
check that the order of configuration does not impact switch behavior.

See more details in the commit messages.

Note that the tests supposed to pass also using the legacy model, they
are added now as with the new model they test the driver and not the
firmware.

Patch set overview:
Patch #1 adds test for {Port, VID} -> FID
Patch #2 adds test for VID -> FID
Patch #3 adds test for VNI -> FID
Patch #4 adds test for egress VID classification

Amit Cohen (4):
  selftests: mlxsw: Add ingress RIF configuration test for 802.1D bridge
  selftests: mlxsw: Add ingress RIF configuration test for 802.1Q bridge
  selftests: mlxsw: Add ingress RIF configuration test for VXLAN
  selftests: mlxsw: Add egress VID classification test

 .../net/mlxsw/egress_vid_classification.sh    | 273 +++++++++++++++
 .../drivers/net/mlxsw/ingress_rif_conf_1d.sh  | 264 +++++++++++++++
 .../drivers/net/mlxsw/ingress_rif_conf_1q.sh  | 264 +++++++++++++++
 .../net/mlxsw/ingress_rif_conf_vxlan.sh       | 311 ++++++++++++++++++
 4 files changed, 1112 insertions(+)
 create mode 100755 tools/testing/selftests/drivers/net/mlxsw/egress_vid_classification.sh
 create mode 100755 tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1d.sh
 create mode 100755 tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1q.sh
 create mode 100755 tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_vxlan.sh

-- 
2.35.3