From: Kunwu Chan <kunwu.chan@linux.dev>
To: corbet@lwn.net, skhan@linuxfoundation.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
paulmck@kernel.org, gustavold@gmail.com,
Kunwu Chan <kunwu.chan@gmail.com>
Subject: [PATCH] docs: Document panic_on_rcu_stall default behavior
Date: Sat, 9 May 2026 17:12:14 +0800 [thread overview]
Message-ID: <20260509091214.1679194-1-kunwu.chan@linux.dev> (raw)
From: Kunwu Chan <kunwu.chan@gmail.com>
Commit ab875b3e179f ("rcu: Add BOOTPARAM_RCU_STALL_PANIC
Kconfig option") made the default value of
kernel.panic_on_rcu_stall depend on
CONFIG_BOOTPARAM_RCU_STALL_PANIC.
Document this in kernel.rst
Signed-off-by: Kunwu Chan <kunwu.chan@gmail.com>
---
Documentation/admin-guide/sysctl/kernel.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
index c6994e55d141..99598a83f830 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Documentation/admin-guide/sysctl/kernel.rst
@@ -948,6 +948,10 @@ panic_on_rcu_stall
When set to 1, calls panic() after RCU stall detection messages. This
is useful to define the root cause of RCU stalls using a vmcore.
+The default value can be configured at build time via
+``CONFIG_BOOTPARAM_RCU_STALL_PANIC``. Runtime updates to this sysctl
+always override the built-in default.
+
= ============================================================
0 Do not panic() when RCU stall takes place, default behavior.
1 panic() after printing RCU stall messages.
--
2.43.0
next reply other threads:[~2026-05-09 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 9:12 Kunwu Chan [this message]
2026-05-10 19:54 ` [PATCH] docs: Document panic_on_rcu_stall default behavior Paul E. McKenney
2026-05-12 8:08 ` Kunwu Chan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260509091214.1679194-1-kunwu.chan@linux.dev \
--to=kunwu.chan@linux.dev \
--cc=corbet@lwn.net \
--cc=gustavold@gmail.com \
--cc=kunwu.chan@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.