From: Lance Yang <lance.yang@linux.dev>
To: Tomas Glozar <tglozar@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Li RongQing <lirongqing@baidu.com>,
Johnny Mnemonic <jm@machine-hall.org>,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Subject: Re: [PATCH] lib/Kconfig.debug: fix BOOTPARAM_HUNG_TASK_PANIC comment
Date: Tue, 6 Jan 2026 23:15:15 +0800 [thread overview]
Message-ID: <be5f89f1-2092-491b-b46b-adae4a6eacc9@linux.dev> (raw)
In-Reply-To: <20260106140140.136446-1-tglozar@redhat.com>
On 2026/1/6 22:01, Tomas Glozar wrote:
> The comment for CONFIG_BOOTPARAM_HUNG_TASK_PANIC says:
>
> Say N if unsure.
>
> but since commit 9544f9e6947f ("hung_task: panic when there are more than N
> hung tasks at the same time"), N is not a valid value for the option,
> leading to a warning at build time:
>
> .config:11736:warning: symbol value 'n' invalid for BOOTPARAM_HUNG_TASK_PANIC
>
> as well as an error when given to menuconfig.
>
> Fix the comment to say '0' instead of 'N'.
>
> Fixes: 9544f9e6947f ("hung_task: panic when there are more than N hung tasks at the same time")
> Reported-by: Johnny Mnemonic <jm@machine-hall.org>
> Signed-off-by: Tomas Glozar <tglozar@redhat.com>
> ---
Thanks!
Reviewed-by: Lance Yang <lance.yang@linux.dev>
> lib/Kconfig.debug | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index ba36939fda79..cda3cf1fa302 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1273,7 +1273,7 @@ config BOOTPARAM_HUNG_TASK_PANIC
> high-availability systems that have uptime guarantees and
> where a hung tasks must be resolved ASAP.
>
> - Say N if unsure.
> + Say 0 if unsure.
>
> config DETECT_HUNG_TASK_BLOCKER
> bool "Dump Hung Tasks Blocker"
prev parent reply other threads:[~2026-01-06 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 14:01 Tomas Glozar
2026-01-06 15:15 ` Lance Yang [this message]
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=be5f89f1-2092-491b-b46b-adae4a6eacc9@linux.dev \
--to=lance.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=jm@machine-hall.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mhiramat@kernel.org \
--cc=pmladek@suse.com \
--cc=tglozar@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®