From: Chris Ball <cjb@laptop.org>
To: Jingoo Han <jg1.han@samsung.com>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: mmc_test: replace strict_strtol() with kstrtol_from_user()
Date: Sat, 24 Aug 2013 23:19:27 -0400 [thread overview]
Message-ID: <87haeesbi8.fsf@octavius.laptop.org> (raw)
In-Reply-To: <000c01ce844d$f75ba650$e612f2f0$@samsung.com> (Jingoo Han's message of "Fri, 19 Jul 2013 16:02:43 +0900")
Hi Jingoo,
On Fri, Jul 19 2013, Jingoo Han wrote:
> The usage of strict_strtol() is not preferred, because
> strict_strtol() is obsolete. Thus, kstrtol() should be
> used.
>
> Also, both kstrtol() and copy_from_user() can be replaced
> with kstrtol_from_user() to make the code simpler.
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
> drivers/mmc/card/mmc_test.c | 14 ++++----------
> 1 file changed, 4 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/mmc/card/mmc_test.c b/drivers/mmc/card/mmc_test.c
> index a69df52..0c0fc52 100644
> --- a/drivers/mmc/card/mmc_test.c
> +++ b/drivers/mmc/card/mmc_test.c
> @@ -2849,18 +2849,12 @@ static ssize_t mtf_test_write(struct file *file, const char __user *buf,
> struct seq_file *sf = (struct seq_file *)file->private_data;
> struct mmc_card *card = (struct mmc_card *)sf->private;
> struct mmc_test_card *test;
> - char lbuf[12];
> long testcase;
> + int ret;
>
> - if (count >= sizeof(lbuf))
> - return -EINVAL;
> -
> - if (copy_from_user(lbuf, buf, count))
> - return -EFAULT;
> - lbuf[count] = '\0';
> -
> - if (strict_strtol(lbuf, 10, &testcase))
> - return -EINVAL;
> + ret = kstrtol_from_user(buf, count, 10, &testcase);
> + if (ret)
> + return ret;
>
> test = kzalloc(sizeof(struct mmc_test_card), GFP_KERNEL);
> if (!test)
Thanks, pushed to mmc-next for 3.12.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
prev parent reply other threads:[~2013-08-25 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 7:02 [PATCH] mmc: mmc_test: replace strict_strtol() with kstrtol_from_user() Jingoo Han
2013-08-25 3:19 ` Chris Ball [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=87haeesbi8.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=jg1.han@samsung.com \
--cc=linux-mmc@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