From: Jeff Liu <jeff.liu@oracle.com>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: replace simple_strtoull() with kstrtoull() in btrfs_ioctl_resize()
Date: Tue, 08 Jan 2013 15:04:50 +0800 [thread overview]
Message-ID: <50EBC512.4020106@oracle.com> (raw)
In-Reply-To: <20130107160350.GI20089@twin.jikos.cz>
On 01/08/2013 12:03 AM, David Sterba wrote:
> On Sun, Jan 06, 2013 at 11:53:41AM +0800, Jeff Liu wrote:
>> - devid = simple_strtoull(devstr, &end, 10);
>> + ret = kstrtoull(devstr, 10, &devid);
>> + if (ret) {
>> + pr_err("btrfs: resizer unable to parse device %s\n",
>> + devstr);
>
> Code looks ok, I would prefer the message error text to say:
>
> pr_err("btrfs: resize unable to parse device id %s\n",
> devstr);
>
> but that's maybe just me :)
Thanks for the review, yours is better :)
The revised patch was shown as following:
simple_strtoull() is obsolete, use kstrtoull() instead.
Signed-off-by: Jie Liu <jeff.liu@oracle.com>
Cc: David Sterba <dsterba@suse.cz>
---
fs/btrfs/ioctl.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index 8fcf9a5..d9045eb 100644
--- a/fs/btrfs/ioctl.c
+++ b/fs/btrfs/ioctl.c
@@ -1331,11 +1331,16 @@ static noinline int btrfs_ioctl_resize(struct btrfs_root *root,
sizestr = vol_args->name;
devstr = strchr(sizestr, ':');
if (devstr) {
- char *end;
sizestr = devstr + 1;
*devstr = '\0';
devstr = vol_args->name;
- devid = simple_strtoull(devstr, &end, 10);
+ ret = kstrtoull(devstr, 10, &devid);
+ if (ret) {
+ pr_err("btrfs: resizer unable to parse device id %s\n",
+ devstr);
+ ret = -EINVAL;
+ goto out_free;
+ }
printk(KERN_INFO "btrfs: resizing devid %llu\n",
(unsigned long long)devid);
}
--
1.7.9.5
prev parent reply other threads:[~2013-01-08 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 3:53 [PATCH] Btrfs: replace simple_strtoull() with kstrtoull() in btrfs_ioctl_resize() Jeff Liu
2013-01-07 16:03 ` David Sterba
2013-01-08 7:04 ` Jeff Liu [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=50EBC512.4020106@oracle.com \
--to=jeff.liu@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).