linux-kernel - [PATCH RFC 0/5] Run stress-ng via rcutorture

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: <20250124015836.732086-1-joel@joelfernandes.org>
Date: Thu, 23 Jan 2025 20:58:31 -0500
From: "Joel Fernandes (Google)" <joel@...lfernandes.org>
To: linux-kernel@...r.kernel.org
Cc: "Joel Fernandes (Google)" <joel@...lfernandes.org>
Subject: [PATCH RFC 0/5] Run stress-ng via rcutorture

These are initial patches I wrote to build and invoke stress-ng from
rcutorture. Last year when I ran 'matrixprod', I could boost the code coverage
in tree.c by ~5% (80 to 85%).

I am planning to run more RCU-strenous loads like stress-ng's 'dirmany'
stressor and collect coverage. Also perhaps we can span more than one stressor
in a default stress-ng invocation to add some variety and concurrency to the
workloads.

Joel Fernandes (Google) (5):
  rcutorture: kvm: Simplify invocation of mkinitrd.sh
  rcutorture: Add a stress-ng build script
  rcutorture: mkinitrd: Allow to run optional commands passed to it
  rcutorture: mkinitrd: Use previous init.c to check if rebuild needed
  rcutorture: kvm: Invoke stress-ng building it if necessary

 tools/testing/selftests/rcutorture/bin/kvm.sh | 39 +++++++--
 .../selftests/rcutorture/bin/mkinitrd.sh      | 59 +++++++++++--
 .../selftests/rcutorture/bin/mkstress-ng.sh   | 86 +++++++++++++++++++
 3 files changed, 171 insertions(+), 13 deletions(-)
 create mode 100755 tools/testing/selftests/rcutorture/bin/mkstress-ng.sh

-- 
2.34.1