linux-kernel - [PATCH 0/2] selftests: bump timeout for firmware and kmod

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: <20230206234344.2433950-1-mcgrof@kernel.org>
Date:   Mon,  6 Feb 2023 15:43:42 -0800
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     shuah@...nel.org, linux-kselftest@...r.kernel.org
Cc:     gregkh@...uxfoundation.org, tiwai@...e.de, tianfei.zhang@...el.com,
        russell.h.weight@...el.com, keescook@...omium.org,
        tweek@...gle.com, a.manzanares@...sung.com, dave@...olabs.net,
        linux-modules@...r.kernel.org, linux-kernel@...r.kernel.org,
        Luis Chamberlain <mcgrof@...nel.org>
Subject: [PATCH 0/2] selftests: bump timeout for firmware and kmod

Shuah,

I'd like this to go through your tree as this is timeout related.

In order to help me help developers run tests against the components
I maintain much easily I have enabled selftests support on kdevops [0].
kdevops deals with abstractsions like letting you pick virtualization
or cloud solutions to run the tests using kconfig, installs all
dependencies for you, and with just a few make target commands can get
you the latest linux-next tested against selftests.

If other find this useful and would like support for their selftests on
kdevops feel free to send patches. Eventually the idea is to be able to
run as many selftests in parallel using different guests for each main
selftest to speed up tests.

Prior to this I used to run tests manually, now the selftests helpers
are used (./tools/testing/selftests/run_kselftest.sh -s) and with this
the default selftest timeout is hit. This just increases that for the few
selftests I help maintain where obviously its not enough anymore.

Note: on the firmware side I am spotting an OOM triggered by running
tests in a loop, so far I hit in the android configuration but its
not clear if the issue is just for that setup.

[0] https://github.com/linux-kdevops/kdevops

Luis Chamberlain (2):
  selftests/kmod: increase the kmod timeout from 45 to 165
  selftests/firmware: increase timeout from 165 to 230

 tools/testing/selftests/firmware/settings | 8 +++++++-
 tools/testing/selftests/kmod/settings     | 4 ++++
 2 files changed, 11 insertions(+), 1 deletion(-)
 create mode 100644 tools/testing/selftests/kmod/settings

-- 
2.39.1