From: Yang Yingliang <yangyingliang@huawei.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-staging@lists.linux.dev>,
<johan@kernel.org>, <elder@kernel.org>,
<gregkh@linuxfoundation.org>
Subject: Re: [PATCH -next] staging: greybus: camera: Switch to memdup_user_nul()
Date: Thu, 1 Apr 2021 10:41:07 +0800 [thread overview]
Message-ID: <74cc6ea7-7b03-dea1-ba02-0ad41df29ced@huawei.com> (raw)
In-Reply-To: <20210331102414.GL2065@kadam>
Hi,
On 2021/3/31 18:24, Dan Carpenter wrote:
> On Wed, Mar 31, 2021 at 05:52:01PM +0800, Yang Yingliang wrote:
>> Use memdup_user_nul() helper instead of open-coding to
>> simplify the code.
>>
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
>> ---
>> drivers/staging/greybus/camera.c | 10 ++--------
>> 1 file changed, 2 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/staging/greybus/camera.c b/drivers/staging/greybus/camera.c
>> index b570e13394ac..0f005facffbc 100644
>> --- a/drivers/staging/greybus/camera.c
>> +++ b/drivers/staging/greybus/camera.c
>> @@ -1120,16 +1120,10 @@ static ssize_t gb_camera_debugfs_write(struct file *file,
>> if (len > 1024)
>> return -EINVAL;
>>
>> - kbuf = kmalloc(len + 1, GFP_KERNEL);
>> - if (!kbuf)
>> + kbuf = memdup_user_nul(buf, len);
>> + if (IS_ERR(kbuf))
>> return -ENOMEM;
> return PTR_ERR(kbuf);
>
>>
>> - if (copy_from_user(kbuf, buf, len)) {
>> - ret = -EFAULT;
>> - goto done;
>> - }
>> -
>> - kbuf[len] = '\0';
>>
> ^^^^^^^^
> Please delete this blank line so there aren't two blank lines in a row.
I will change it and send a v2.
Thanks,
Yang
>
>> ret = op->execute(gcam, kbuf, len);
> regards,
> dan carpenter
>
> .
prev parent reply other threads:[~2021-04-01 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 9:52 Yang Yingliang
2021-03-31 10:24 ` Dan Carpenter
2021-04-01 2:41 ` Yang Yingliang [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=74cc6ea7-7b03-dea1-ba02-0ad41df29ced@huawei.com \
--to=yangyingliang@huawei.com \
--cc=dan.carpenter@oracle.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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
all inboxes | Powered by JetHome®