From: Ingo Molnar <mingo@kernel.org>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH try2] panic: setup panic_timeout early
Date: Mon, 11 Nov 2013 15:16:40 +0100 [thread overview]
Message-ID: <20131111141640.GA10124@gmail.com> (raw)
In-Reply-To: <1384177186-23716-1-git-send-email-felipe.contreras@gmail.com>
* Felipe Contreras <felipe.contreras@gmail.com> wrote:
> Otherwise we might not reboot when the user needs it the most (early
> on).
>
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> ---
>
> This is exactly the same as in the previous try, but now alone since it was
> mudded by largely irrelevant patches in the series.
>
> kernel/panic.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/panic.c b/kernel/panic.c
> index b6c482c..46e37ff 100644
> --- a/kernel/panic.c
> +++ b/kernel/panic.c
> @@ -468,9 +468,21 @@ EXPORT_SYMBOL(__stack_chk_fail);
>
> #endif
>
> -core_param(panic, panic_timeout, int, 0644);
> core_param(pause_on_oops, pause_on_oops, int, 0644);
>
> +static int __init set_panic_timeout(char *str)
> +{
> + int timeout;
> +
> + if (!get_option(&str, &timeout))
> + return -EINVAL;
> +
> + panic_timeout = timeout;
> + return 0;
> +}
> +
> +early_param("panic_timeout", set_panic_timeout);
> +
This still has the problem I pointed out for your v1 patch: for simple
integer parameters simple_strtol() is better and (a tiny bit) faster.
Thanks,
Ingo
prev parent reply other threads:[~2013-11-11 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 13:39 [PATCH try2] panic: setup panic_timeout early Felipe Contreras
2013-11-11 14:16 ` Ingo Molnar [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=20131111141640.GA10124@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=felipe.contreras@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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