All of lore.kernel.org
 help / color / mirror / Atom feed
From: He Zhe <zhe.he@windriver.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>,
	<x86@kernel.org>, <pombredanne@nexb.com>,
	<gregkh@linuxfoundation.org>, <kstewart@linuxfoundation.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] x86: corruption-check: Passing memory_corruption_check to command line causes panic
Date: Mon, 20 Aug 2018 16:56:22 +0800	[thread overview]
Message-ID: <129aaffb-7f8d-cf84-cf2d-8e95e303908a@windriver.com> (raw)
In-Reply-To: <1534260823-87917-1-git-send-email-zhe.he@windriver.com>

Could you please provide your input? Thanks.

Zhe

On 2018年08月14日 23:33, zhe.he@windriver.com wrote:
> From: He Zhe <zhe.he@windriver.com>
>
> memory_corruption_check[{_period|_size}]'s handlers do not check input
> argument before passing it to kstrtoul or simple_strtoull. The argument
> would be a NULL pointer if each of the kernel parameters, without its
> value, is set in command line and thus cause the following panic.
>
> PANIC: early exception 0xe3 IP 10:ffffffff73587c22 error 0 cr2 0x0
> [    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.18-rc8+ #2
> [    0.000000] RIP: 0010:kstrtoull+0x2/0x10
> ...
> [    0.000000] Call Trace
> [    0.000000]  ? set_corruption_check+0x21/0x49
> [    0.000000]  ? do_early_param+0x4d/0x82
> [    0.000000]  ? parse_args+0x212/0x330
> [    0.000000]  ? rdinit_setup+0x26/0x26
> [    0.000000]  ? parse_early_options+0x20/0x23
> [    0.000000]  ? rdinit_setup+0x26/0x26
> [    0.000000]  ? parse_early_param+0x2d/0x39
> [    0.000000]  ? setup_arch+0x2f7/0xbf4
> [    0.000000]  ? start_kernel+0x5e/0x4c2
> [    0.000000]  ? load_ucode_bsp+0x113/0x12f
> [    0.000000]  ? secondary_startup_64+0xa5/0xb0
>
> This patch adds checks to prevent the panic.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: He Zhe <zhe.he@windriver.com>
> ---
> v2:
> - Split out printk cleanups
> - Add cc to stable@vger.kernel.org
> - Use more meaningful error message
>
>  arch/x86/kernel/check.c | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
>
> diff --git a/arch/x86/kernel/check.c b/arch/x86/kernel/check.c
> index 3339942..cc8258a 100644
> --- a/arch/x86/kernel/check.c
> +++ b/arch/x86/kernel/check.c
> @@ -31,6 +31,11 @@ static __init int set_corruption_check(char *arg)
>  	ssize_t ret;
>  	unsigned long val;
>  
> +	if (!arg) {
> +		pr_err("memory_corruption_check config string not provided\n");
> +		return -EINVAL;
> +	}
> +
>  	ret = kstrtoul(arg, 10, &val);
>  	if (ret)
>  		return ret;
> @@ -45,6 +50,11 @@ static __init int set_corruption_check_period(char *arg)
>  	ssize_t ret;
>  	unsigned long val;
>  
> +	if (!arg) {
> +		pr_err("memory_corruption_check_period config string not provided\n");
> +		return -EINVAL;
> +	}
> +
>  	ret = kstrtoul(arg, 10, &val);
>  	if (ret)
>  		return ret;
> @@ -59,6 +69,11 @@ static __init int set_corruption_check_size(char *arg)
>  	char *end;
>  	unsigned size;
>  
> +	if (!arg) {
> +		pr_err("memory_corruption_check_size config string not provided\n");
> +		return -EINVAL;
> +	}
> +
>  	size = memparse(arg, &end);
>  
>  	if (*end == '\0')


  parent reply	other threads:[~2018-08-20  8:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14 15:33 [PATCH v2 1/2] x86: corruption-check: Passing memory_corruption_check to command line causes panic zhe.he
2018-08-14 15:33 ` [PATCH v2 2/2] x86: corruption-check: Change printk to the right fashion zhe.he
2018-09-11  6:19   ` [tip:x86/boot] x86/corruption-check: Use pr_*() instead of printk() tip-bot for He Zhe
2018-08-20  8:56 ` He Zhe [this message]
2018-08-20 17:18   ` [PATCH v2 1/2] x86: corruption-check: Passing memory_corruption_check to command line causes panic Greg KH
2018-09-11  6:18 ` [tip:x86/boot] x86/corruption-check: Fix panic in memory_corruption_check() when boot option without value is provided tip-bot for He Zhe

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=129aaffb-7f8d-cf84-cf2d-8e95e303908a@windriver.com \
    --to=zhe.he@windriver.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pombredanne@nexb.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 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.