public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Mallon <ryan@bluewatersys.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
	rusty@rustcorp.com.au, adobriyan@gmail.com
Subject: Re: [PATCH 2/3] debugfs: move to new kstrtobool function
Date: Thu, 24 Mar 2011 09:20:07 +1300	[thread overview]
Message-ID: <4D8A55F7.1070802@bluewatersys.com> (raw)
In-Reply-To: <1300887554-19031-3-git-send-email-jic23@cam.ac.uk>

On 03/24/2011 02:39 AM, Jonathan Cameron wrote:
> No functional changes requires that we eat errors from
> kstrtobool.  Note *val is still only updated if a valid
> input is found.
> 
> Signed-off-by: Jonathan Cameron <jic23@cam.ac.uk>
> ---
>  fs/debugfs/file.c |   19 ++++++-------------
>  1 files changed, 6 insertions(+), 13 deletions(-)
> 
> diff --git a/fs/debugfs/file.c b/fs/debugfs/file.c
> index 89d394d..fed4485 100644
> --- a/fs/debugfs/file.c
> +++ b/fs/debugfs/file.c
> @@ -429,25 +429,18 @@ static ssize_t write_file_bool(struct file *file, const char __user *user_buf,
>  {
>  	char buf[32];
>  	int buf_size;
> +	int ret;
> +	bool bv;
>  	u32 *val = file->private_data;
>  
>  	buf_size = min(count, (sizeof(buf)-1));
>  	if (copy_from_user(buf, user_buf, buf_size))
>  		return -EFAULT;
>  
> -	switch (buf[0]) {
> -	case 'y':
> -	case 'Y':
> -	case '1':
> -		*val = 1;
> -		break;
> -	case 'n':
> -	case 'N':
> -	case '0':
> -		*val = 0;
> -		break;
> -	}
> -	
> +	ret = kstrtobool(buf, &bv);
> +	if (!ret)
> +		*val = bv;
> +
>  	return count;

Shouldn't this be:

	ret = kstrtobool(buf, &bv);
	if (ret)
		return ret;

	*val = bv;
	return count;

?

~Ryan

-- 
Bluewater Systems Ltd - ARM Technology Solution Centre

Ryan Mallon         		5 Amuri Park, 404 Barbadoes St
ryan@bluewatersys.com         	PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com	New Zealand
Phone: +64 3 3779127		Freecall: Australia 1800 148 751
Fax:   +64 3 3779135			  USA 1800 261 2934

  reply	other threads:[~2011-03-23 20:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 13:39 [RFC PATCH 0/3] Introduce kstrtobool function Jonathan Cameron
2011-03-23 13:39 ` [PATCH 1/3] Add a kstrtobool function matching semantics of existing in kernel equivalents Jonathan Cameron
2011-03-23 13:54   ` David Sterba
2011-03-23 14:00     ` Jonathan Cameron
2011-03-23 15:30   ` Alexey Dobriyan
2011-03-23 16:01     ` Greg KH
2011-03-23 16:15       ` Jonathan Cameron
2011-03-23 16:23         ` Greg KH
2011-03-23 16:37           ` Jonathan Cameron
2011-03-23 18:44             ` Greg KH
2011-03-23 19:11               ` Jonathan Cameron
2011-03-23 13:39 ` [PATCH 2/3] debugfs: move to new kstrtobool function Jonathan Cameron
2011-03-23 20:20   ` Ryan Mallon [this message]
2011-03-24 10:53     ` Jonathan Cameron
2011-03-23 13:39 ` [PATCH 3/3] params.c: Use new kstrtobool implementation to processing boolean inputs Jonathan Cameron
2011-03-23 13:42   ` Jonathan Cameron
2011-03-24  0:34 ` [RFC PATCH 0/3] Introduce kstrtobool function Rusty Russell

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=4D8A55F7.1070802@bluewatersys.com \
    --to=ryan@bluewatersys.com \
    --cc=adobriyan@gmail.com \
    --cc=greg@kroah.com \
    --cc=jic23@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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