mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: Brian Masney <bmasney@redhat.com>, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/Kconfig.debug: document panic= command line option for PANIC_TIMEOUT
Date: Wed, 05 Jun 2024 20:05:23 +0200	[thread overview]
Message-ID: <87wmn3nu3g.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <20240605174736.778321-1-bmasney@redhat.com>

Brian Masney <bmasney@redhat.com> writes:

Hello Brian,

> PANIC_TIMEOUT can also be controlled with the panic= kernel command line
> option, so let's reference it in the Kconfig help. This option is already
> documented in kernel-parameters.txt.
>
> Signed-off-by: Brian Masney <bmasney@redhat.com>
> ---
>  lib/Kconfig.debug | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 59b6765d86b8..a6eb7425b888 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1043,7 +1043,8 @@ config PANIC_TIMEOUT
>  	  Set the timeout value (in seconds) until a reboot occurs when
>  	  the kernel panics. If n = 0, then we wait forever. A timeout
>  	  value n > 0 will wait n seconds before rebooting, while a timeout
> -	  value n < 0 will reboot immediately.
> +	  value n < 0 will reboot immediately. The kernel command line
> +	  option panic= may be used to override this option.
>  

Thanks for adding this, I wasn't aware of that panic= cmdline before.

Maybe it could also be mentioned that the timeout can be overriden by
user-space using the /proc/sys/kernel/panic sysfs entry too ?

Regardless, the patch looks good to me.

Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>

-- 
Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat


  reply	other threads:[~2024-06-05 18:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 17:47 Brian Masney
2024-06-05 18:05 ` Javier Martinez Canillas [this message]
2024-06-05 18:11   ` Brian Masney

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=87wmn3nu3g.fsf@minerva.mail-host-address-is-not-set \
    --to=javierm@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bmasney@redhat.com \
    --cc=linux-kernel@vger.kernel.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 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®