Messages in this thread Patch in this message | | | Date | Fri, 12 Feb 2021 12:37:25 -0000 | From | "tip-bot2 for Paul E. McKenney" <> | Subject | [tip: core/rcu] torture: Stop hanging on panic |
| |
The following commit has been merged into the core/rcu branch of tip:
Commit-ID: f716348f29d30e8ef3a1ceed3fea19490aba4fe4 Gitweb: https://git.kernel.org/tip/f716348f29d30e8ef3a1ceed3fea19490aba4fe4 Author: Paul E. McKenney <paulmck@kernel.org> AuthorDate: Thu, 03 Dec 2020 13:27:42 -08:00 Committer: Paul E. McKenney <paulmck@kernel.org> CommitterDate: Mon, 04 Jan 2021 14:01:23 -08:00
torture: Stop hanging on panic
By default, the "panic" kernel parameter is zero, which causes the kernel to loop indefinitely after a panic(). The rcutorture scripting will eventually kill the corresponding qemu process, but only after waiting for the full run duration plus a few minutes. This works, but delays notifying the developer of the failure.
This commit therefore causes the rcutorture scripting to pass the "panic=-1" kernel parameter, which caused the kernel to instead unceremoniously shut down immediately. This in turn causes qemu to terminate, so that if all of the runs in a given batch panic(), the rcutorture scripting can immediately proceed to the next batch.
Signed-off-by: Paul E. McKenney <paulmck@kernel.org> --- tools/testing/selftests/rcutorture/bin/functions.sh | 1 + 1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/rcutorture/bin/functions.sh b/tools/testing/selftests/rcutorture/bin/functions.sh index 97c3a17..c35ba24 100644 --- a/tools/testing/selftests/rcutorture/bin/functions.sh +++ b/tools/testing/selftests/rcutorture/bin/functions.sh @@ -203,6 +203,7 @@ identify_qemu () { # and the TORTURE_QEMU_INTERACTIVE environment variable. identify_qemu_append () { echo debug_boot_weak_hash + echo panic=-1 local console=ttyS0 case "$1" in qemu-system-x86_64|qemu-system-i386)
| |