public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: zhong jiang <zhongjiang@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <martin.petersen@oracle.com>, <Don.Brace@microchip.com>,
	<don.brace@microsemi.com>, <jejb@linux.vnet.ibm.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] scsi: Use vmemdup_user to replace the open code
Date: Tue, 18 Sep 2018 23:00:37 +0800	[thread overview]
Message-ID: <5BA11315.4060908@huawei.com> (raw)
In-Reply-To: <5B7E9CCE.5010007@huawei.com>

Hi,  Greg

Can you pick up the patch?

Thanks,
zhong jiang

On 2018/8/23 19:38, zhong jiang wrote:
> On 2018/8/13 22:20, Don.Brace@microchip.com wrote:
>>> -----Original Message-----
>>> From: zhong jiang [mailto:zhongjiang@huawei.com]
>>> Sent: Monday, August 13, 2018 7:43 AM
>>> To: don.brace@microsemi.com; jejb@linux.vnet.ibm.com;
>>> martin.petersen@oracle.com
>>> Cc: linux-kernel@vger.kernel.org
>>> Subject: [PATCH v2] scsi: Use vmemdup_user to replace the open code
>>>
>>> EXTERNAL EMAIL
>>>
>>>
>>> EXTERNAL EMAIL
>>>
>>>
>>> vmemdup_user is better than duplicating its implementation, So just
>>> replace the open code.
>>>
>>> The issue is detected with the help of Coccinelle.
>>>
>>> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
>> Tested-by: Don Brace <don.brace@microsemi.com>
>> Acked-by: Don Brace <don.brace@microsemi.com>
>  Thanks Don for your test and ack.
>  
>  Martin ,  Can you pick up the patch, Thanks
>
>  Best wishes,
>  zhong jiang
>>> ---
>>>  drivers/scsi/hpsa.c | 12 ++++--------
>>>  1 file changed, 4 insertions(+), 8 deletions(-)
>>>
>>> diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
>>> index 58bb70b..666ba09e5 100644
>>> --- a/drivers/scsi/hpsa.c
>>> +++ b/drivers/scsi/hpsa.c
>>> @@ -6381,13 +6381,9 @@ static int hpsa_big_passthru_ioctl(struct ctlr_info
>>> *h, void __user *argp)
>>>                 return -EINVAL;
>>>         if (!capable(CAP_SYS_RAWIO))
>>>                 return -EPERM;
>>> -       ioc = kmalloc(sizeof(*ioc), GFP_KERNEL);
>>> -       if (!ioc) {
>>> -               status = -ENOMEM;
>>> -               goto cleanup1;
>>> -       }
>>> -       if (copy_from_user(ioc, argp, sizeof(*ioc))) {
>>> -               status = -EFAULT;
>>> +       ioc = vmemdup_user(argp, sizeof(*ioc));
>>> +       if (IS_ERR(ioc)) {
>>> +               status = PTR_ERR(ioc);
>>>                 goto cleanup1;
>>>         }
>>>         if ((ioc->buf_size < 1) &&
>>> @@ -6505,7 +6501,7 @@ static int hpsa_big_passthru_ioctl(struct ctlr_info *h,
>>> void __user *argp)
>>>                 kfree(buff);
>>>         }
>>>         kfree(buff_size);
>>> -       kfree(ioc);
>>> +       kvfree(ioc);
>>>         return status;
>>>  }
>>>
>>> --
>>> 1.7.12.4
>>
>
>
> .
>



  reply	other threads:[~2018-09-18 15:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 12:43 [PATCH v2] scsi: Use vmemdup_user to replace the open code zhong jiang
2018-08-13 14:20 ` Don.Brace
2018-08-23 11:38   ` zhong jiang
2018-09-18 15:00     ` zhong jiang [this message]
2018-09-18 15:09       ` Martin K. Petersen
2018-09-18 15:13         ` zhong jiang
2018-09-18 15:10       ` Greg KH
2018-09-18 15:34         ` zhong jiang

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=5BA11315.4060908@huawei.com \
    --to=zhongjiang@huawei.com \
    --cc=Don.Brace@microchip.com \
    --cc=don.brace@microsemi.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    /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