netdev - [PATCH net-next v1 0/3] selftests: rds selftest

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: <20240626012834.5678-1-allison.henderson@oracle.com>
Date: Tue, 25 Jun 2024 18:28:31 -0700
From: allison.henderson@...cle.com
To: netdev@...r.kernel.org
Cc: linux-kselftest@...r.kernel.org, rds-devel@....oracle.com,
        linux-rdma@...r.kernel.org, oberpar@...ux.ibm.com,
        chuck.lever@...cle.com, vegard.nossum@...cle.com,
        Allison Henderson <allison.henderson@...cle.com>
Subject: [PATCH net-next v1 0/3] selftests: rds selftest

From: Allison Henderson <allison.henderson@...cle.com>

Hi All,

This series is a new selftest that Vegard, Chuck and myself have been
working on to provide some test coverage for rds.  I've made quite a few
updates since the rfc sent a few weeks ago:

  I've added several knobs to the script to tune network turbulance, and
  documented their usage in the README.txt.  By default these options
  are left off.

  Added an extra flag to specify log location

  I've also added a flag to the config.sh to skip gcov configurations if
  the coverage report is not desired.  run.sh has been adapted to skip
  the report if the required configs are not present, or if the required
  packages are not available

  A time out has been added to prevent the test from hanging
  indefinitely

  The previous gcov issues have been resolved with an appropriate gcov
  patch, as well as some extra logic to detect incompatible gcov and gcc
  versions.

  The shellcheck nits reported in the last review have been addressed

  In order to return an appropriate exit code, the run.sh script has
  been adapted to analyze the test.py strace, and determine if the test
  passed, failed or timed out.

  RDS specific GCOV configs have been documented under
  Documentation/dev-tools/gcov.rst

Questions and comments appreciated.  Thanks everyone!

Allison

Vegard Nossum (3):
  .gitignore: add .gcda files
  net: rds: add option for GCOV profiling
  selftests: rds: add testing infrastructure

 .gitignore                                 |   1 +
 Documentation/dev-tools/gcov.rst           |  11 +
 MAINTAINERS                                |   1 +
 net/rds/Kconfig                            |   9 +
 net/rds/Makefile                           |   5 +
 tools/testing/selftests/Makefile           |   1 +
 tools/testing/selftests/net/rds/Makefile   |  13 +
 tools/testing/selftests/net/rds/README.txt |  41 ++++
 tools/testing/selftests/net/rds/config.sh  |  56 +++++
 tools/testing/selftests/net/rds/init.sh    |  69 ++++++
 tools/testing/selftests/net/rds/run.sh     | 271 +++++++++++++++++++++
 tools/testing/selftests/net/rds/test.py    | 251 +++++++++++++++++++
 12 files changed, 729 insertions(+)
 create mode 100644 tools/testing/selftests/net/rds/Makefile
 create mode 100644 tools/testing/selftests/net/rds/README.txt
 create mode 100755 tools/testing/selftests/net/rds/config.sh
 create mode 100755 tools/testing/selftests/net/rds/init.sh
 create mode 100755 tools/testing/selftests/net/rds/run.sh
 create mode 100644 tools/testing/selftests/net/rds/test.py

-- 
2.25.1