| 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
| ||
|
Message-ID: <6ea3231d-d131-4431-bd72-9dbb1e4410c9@infradead.org> Date: Mon, 22 Sep 2025 21:35:32 -0700 From: Randy Dunlap <rdunlap@...radead.org> To: lirongqing <lirongqing@...du.com>, corbet@....net, akpm@...ux-foundation.org, lance.yang@...ux.dev, mhiramat@...nel.org, paulmck@...nel.org, pawan.kumar.gupta@...ux.intel.com, mingo@...nel.org, dave.hansen@...ux.intel.com, rostedt@...dmis.org, kees@...nel.org, arnd@...db.de, feng.tang@...ux.alibaba.com, pauld@...hat.com, joel.granados@...nel.org, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH][RFC] hung_task: Support to panic when the maximum number of hung task warnings is reached On 9/22/25 8:37 PM, lirongqing wrote: > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index dc0e0c6..e7cf166 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -1264,10 +1264,10 @@ config DEFAULT_HUNG_TASK_TIMEOUT > Keeping the default should be fine in most cases. > > config BOOTPARAM_HUNG_TASK_PANIC > - bool "Panic (Reboot) On Hung Tasks" > + int "Panic (Reboot) On Hung Tasks" > depends on DETECT_HUNG_TASK > help > - Say Y here to enable the kernel to panic on "hung tasks", > + Say 1|2 here to enable the kernel to panic on "hung tasks", Please make that "1|2" more user-friendly, e.g., "1 or 2". > which are bugs that cause the kernel to leave a task stuck > in uninterruptible "D" state. -- ~Randy
Powered by blists - more mailing lists