aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/torture.c
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@kernel.org>2020-09-21 13:18:48 -0700
committerPaul E. McKenney <paulmck@kernel.org>2020-11-06 17:13:54 -0800
commitc1e06287583e5ec496e4c02bf5b319e5e41a1fd2 (patch)
tree417fc0cca695f21e21ec742813612f1a1de40240 /kernel/torture.c
parentrcutorture: Prevent hangs for invalid arguments (diff)
downloadlinux-dev-c1e06287583e5ec496e4c02bf5b319e5e41a1fd2.tar.xz
linux-dev-c1e06287583e5ec496e4c02bf5b319e5e41a1fd2.zip
torture: Force weak-hashed pointers on console log
Although the rcutorture scripting now deals correctly with full-up security-induced pointer obfuscation, it is still counter-productive for kernel hackers who are analyzing console output. This commit therefore sets the debug_boot_weak_hash kernel boot parameter, which enables printing of weak-hashed pointers for torture-test runs. Please note that this change applies only to runs initiated by the kvm.sh scripting. If you are instead using modprobe and rmmod, it is your responsibility to build and boot the underlying kernel to your taste. Please note further that this change does not result in a security hole in normal use. The rcutorture testing runs with a negligible userspace, no networking, and no user interaction. Besides which, there is no data of value that can be extracted from an rcutorture guest OS that could not also be extracted from the host that this guest is running on. Suggested-by: Anna-Maria Gleixner <anna-maria@linutronix.de> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'kernel/torture.c')
0 files changed, 0 insertions, 0 deletions