linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hangyu Hua <hbh25y@gmail.com>
To: Oliver Neukum <oneukum@suse.com>,
	gregkh@linuxfoundation.org, mudongliangabcd@gmail.com
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: misc: fix improper handling of refcount in uss720_probe()
Date: Thu, 7 Apr 2022 09:55:23 +0800	[thread overview]
Message-ID: <4d0652cd-e3ca-4319-b012-142a110efe15@gmail.com> (raw)
In-Reply-To: <f90522c4-f7d6-3068-9789-8c6d893f2768@suse.com>

Oh, i sorry. Thank you for your reminder. I will remake a patch carefully.

On 2022/4/6 19:47, Oliver Neukum wrote:
> 
> 
> On 06.04.22 09:33, Hangyu Hua wrote:
>> usb_put_dev shouldn't be called when uss720_probe succeeds because of
>> priv->usbdev. At the same time, priv->usbdev shouldn't be set to NULL
>> before destroy_priv in uss720_disconnect because usb_put_dev is in
>> destroy_priv.
> 
> Hi,
> 
> I am sorry, but that's a clear NACK.
>> @@ -754,13 +753,13 @@ static void uss720_disconnect(struct usb_interface *intf)
>>   	usb_set_intfdata(intf, NULL);
>>   	if (pp) {
>>   		priv = pp->private_data;
>> -		priv->usbdev = NULL;
>>   		priv->pp = NULL;
>>   		dev_dbg(&intf->dev, "parport_remove_port\n");
>>   		parport_remove_port(pp);
>>   		parport_put_port(pp);
>>   		kill_all_async_requests_priv(priv);
>>   		kref_put(&priv->ref_count, destroy_priv);
>> +		priv->usbdev = NULL;
> 
> That is a clear use after free The patch is no good in this state..
> 
>      HTH
>          Oliver
> 

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  7:33 [PATCH] usb: misc: fix improper handling of refcount in uss720_probe() Hangyu Hua
2022-04-06 11:47 ` Oliver Neukum
2022-04-07  1:55   ` 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=4d0652cd-e3ca-4319-b012-142a110efe15@gmail.com \
    --to=hbh25y@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mudongliangabcd@gmail.com \
    --cc=oneukum@suse.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;
as well as URLs for NNTP newsgroup(s).