mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hangyu Hua <hbh25y@gmail.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
	valentina.manea.m@gmail.com, shuah@kernel.org,
	gregkh@linuxfoundation.org, khoroshilov@ispras.ru
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: usbip: fix a refcount leak in stub_probe()
Date: Thu, 7 Apr 2022 09:41:41 +0800	[thread overview]
Message-ID: <732eed82-18eb-c57b-fca1-e1f33f1f0499@gmail.com> (raw)
In-Reply-To: <4341150b-195c-a896-1f6a-8715bbb539e2@linuxfoundation.org>

Thanks. I will send a v2.

On 2022/4/7 02:13, Shuah Khan wrote:
> On 4/6/22 12:17 AM, Hangyu Hua wrote:
>> usb_get_dev is called in stub_device_alloc. When stub_probe fails after
>> that, usb_put_dev needs to be used.
>>
> 
> Thank you for the patch. Please include details on how you found
> this problem.
> 
> Nit: Change this to:
> 
> usb_get_dev() is called in stub_device_alloc(). When stub_probe() fails
> after that, usb_put_dev() needs to be called to release the reference.
> 
>> Fix this by moving usb_put_dev() to sdev_free
>>
> 
> Nit: Change this to:
> 
> Fix this by moving usb_put_dev() to sdev_free error path handling.
> 
>> Fixes: 3ff67445750a ("usbip: fix error handling in stub_probe()")
>> Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
>> ---
>>   drivers/usb/usbip/stub_dev.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/usb/usbip/stub_dev.c b/drivers/usb/usbip/stub_dev.c
>> index d8d3892e5a69..3c6d452e3bf4 100644
>> --- a/drivers/usb/usbip/stub_dev.c
>> +++ b/drivers/usb/usbip/stub_dev.c
>> @@ -393,7 +393,6 @@ static int stub_probe(struct usb_device *udev)
>>   err_port:
>>       dev_set_drvdata(&udev->dev, NULL);
>> -    usb_put_dev(udev);
>>       /* we already have busid_priv, just lock busid_lock */
>>       spin_lock(&busid_priv->busid_lock);
>> @@ -408,6 +407,7 @@ static int stub_probe(struct usb_device *udev)
>>       put_busid_priv(busid_priv);
>>   sdev_free:
>> +    usb_put_dev(udev);
>>       stub_device_free(sdev);
>>       return rc;
>>
> 
> With the above addressed:
> 
> Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
> 
> thanks,
> -- Shuah

      reply	other threads:[~2022-04-07  1:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  6:17 Hangyu Hua
2022-04-06 18:13 ` Shuah Khan
2022-04-07  1:41   ` Hangyu Hua [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=732eed82-18eb-c57b-fca1-e1f33f1f0499@gmail.com \
    --to=hbh25y@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=khoroshilov@ispras.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=valentina.manea.m@gmail.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

all inboxes | Powered by JetHome®