linux-kernel - What should we be doing to stress-test kfree

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: <20200401184415.GA7619@paulmck-ThinkPad-P72>
Date:   Wed, 1 Apr 2020 11:44:15 -0700
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     urezki@...il.com, joel@...lfernandes.org
Cc:     linux-kernel@...r.kernel.org, rcu@...r.kernel.org
Subject: What should we be doing to stress-test kfree_rcu()?

Hello!

What should we be doing to stress-test kfree_rcu(), including its ability
to cope with OOM conditions?  Yes, rcuperf runs are nice, but they are not
currently doing much more than testing base functionality, performance,
and scalability.

							Thanx, Paul