linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>, WANG Chao <chaowang@redhat.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/4] x86, kdump: Change crashkernel_high/low= to crashkernel=,high/low
Date: Fri, 12 Apr 2013 14:46:26 +0900	[thread overview]
Message-ID: <51679FB2.9080309@jp.fujitsu.com> (raw)
In-Reply-To: <1365622759-2133-5-git-send-email-yinghai@kernel.org>

(2013/04/11 4:39), Yinghai Lu wrote:
<cut>
> Index: linux-2.6/kernel/kexec.c
> ===================================================================
> --- linux-2.6.orig/kernel/kexec.c
> +++ linux-2.6/kernel/kexec.c
> @@ -1368,35 +1368,108 @@ static int __init parse_crashkernel_simp
>   	return 0;
>   }
>   
> +#define SUFFIX_HIGH 0
> +#define SUFFIX_LOW  1
> +#define SUFFIX_NULL 2
> +static __initdata char *suffix_tbl[] = {
> +	[SUFFIX_HIGH] = ",high",
> +	[SUFFIX_LOW]  = ",low",
> +	[SUFFIX_NULL] = NULL,
> +};
> +
>   /*
> - * That function is the entry point for command line parsing and should be
> - * called from the arch-specific code.
> + * That function parses "suffix"  crashkernel command lines like
> + *
> + *	crashkernel=size,[high|low]
> + *
> + * It returns 0 on success and -EINVAL on failure.
>    */
> +static int __init parse_crashkernel_suffix(char *cmdline,
> +					   unsigned long long	*crash_size,
> +					   unsigned long long	*crash_base,
> +					   const char *suffix)
> +{
> +	char *cur = cmdline;
> +
> +	*crash_size = memparse(cmdline, &cur);
> +	if (cmdline == cur) {
> +		pr_warn("crashkernel: memory value expected\n");
> +		return -EINVAL;
> +	}
> +
> +	/* check with suffix */
> +	if (!strncmp(cur, suffix, strlen(suffix)))
> +		return 0;

What kind of strings do you intend to be passed here? The syntax that
matches this check would be

  [0-9]+[kmgKMG]?(,low|,high){.*(,low|,high)}*

though memparse() part might be less precise. For example, the following
one passes the check since it ends with ",low" and  ",high" follows
"12345K" to be parsed by memparse(). Is this within your intension for
ease of implementation?

  crashkernel=12345K,highfoobar,highabcd,low

> +
> +	pr_warn("crashkernel: unrecognized char\n");
> +	return -EINVAL;
> +}

I like functions checking errornous cases in the middle and ends with
successful case. How about:

/* check with suffix */
if (strncmp(cur, suffix, strlen(suffix)) {
    pr_warn("crashkernel: unrecognized char\n");
    return -EINVAL;
}

return 0;

-- 
Thanks.
HATAYAMA, Daisuke


  reply	other threads:[~2013-04-12  5:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 19:39 [PATCH -v4 0/4] x86, kdump: Fix crashkernel high with old kexec-tools Yinghai Lu
2013-04-10 19:39 ` [PATCH v4 1/4] x86, kdump: Set crashkernel_low automatically Yinghai Lu
2013-04-10 19:39 ` [PATCH v4 4/4] kexec: use Crash kernel for Crash kernel low Yinghai Lu
2013-04-10 19:39 ` [PATCH v4 2/4] x86, kdump: Retore crashkernel= to allocate under 896M Yinghai Lu
2013-04-10 19:39 ` [PATCH v4 3/4] x86, kdump: Change crashkernel_high/low= to crashkernel=,high/low Yinghai Lu
2013-04-12  5:46   ` HATAYAMA Daisuke [this message]
2013-04-12  6:26     ` Yinghai Lu
2013-04-10 20:28 ` [PATCH -v4 0/4] x86, kdump: Fix crashkernel high with old kexec-tools Vivek Goyal
  -- strict thread matches above, loose matches on Subject: below --
2013-04-09 20:01 [PATCH v4 3/4] x86, kdump: Change crashkernel_high/low= to crashkernel=,high/low Yinghai Lu
2013-04-10 19:14 ` Vivek Goyal

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=51679FB2.9080309@jp.fujitsu.com \
    --to=d.hatayama@jp.fujitsu.com \
    --cc=chaowang@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=vgoyal@redhat.com \
    --cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).