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: <c03b8bf87f6a1a1c19647832db0e3fa294eec773.camel@oracle.com>
Date: Sun, 9 Jun 2024 18:08:12 +0000
From: Allison Henderson <allison.henderson@...cle.com>
To: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: "rds-devel@....oracle.com" <rds-devel@....oracle.com>,
        Vegard Nossum
	<vegard.nossum@...cle.com>,
        "oberpar@...ux.ibm.com" <oberpar@...ux.ibm.com>,
        Chuck Lever III <chuck.lever@...cle.com>
Subject: Re: [RFC net-next 0/3] selftests: rds selftest

On Thu, 2024-06-06 at 17:36 -0700, allison.henderson@...cle.com wrote:
+cc Chuck Lever, Peter Oberparleiter, Vegard Nossum, rds-devel

> 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.  It still has a few
> bugs to work out, so it's not quite ready for submission yet.  But we
> thought an RFC would be a good idea just to collect some feed back to
> see what people think.  Some things to be aware of that we are still
> working through:
> 
>   Occasionally we see intermittent hangs during the send and recv.
>   So we still need to track down and address the cause
> 
>   We may still add a time out to handle unexpected hangs
> 
>   We've been having some trouble getting gcov to generate a report if
>   the version of gcov doesn't match the version of gcc installed.  So
>   we may further adapt the test to omit the coverage report if the
>   required dependencies are not met
> 
>   Some distros are still not collecting meaningfull gcda data and
>   generate an empty report, so we are still trying to figure out the
>   cause of that
> 
>   May still add more exit codes for PASS/FAIL/BROKEN/CONFIG
> conditions
> 
> 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 +
>  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 |  15 ++
>  tools/testing/selftests/net/rds/config.sh  |  33 +++
>  tools/testing/selftests/net/rds/init.sh    |  49 +++++
>  tools/testing/selftests/net/rds/run.sh     | 168 ++++++++++++++
>  tools/testing/selftests/net/rds/test.py    | 244
> +++++++++++++++++++++
>  11 files changed, 539 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
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ