All of lore.kernel.org
 help / color / mirror / Atom feed
From: guido@kiener-muenchen.de
To: dpenkler@gmail.com
Cc: linux-usb@vger.kernel.org, lyl2019@mail.ustc.edu.cn,
	guido.kiener@rohde-schwarz.com, gregkh@linuxfoundation.org
Subject: Re: [PATCH v2] usb: Add a lock when freeing data in usbtmc_disconnect
Date: Wed, 14 Apr 2021 15:10:07 +0000	[thread overview]
Message-ID: <20210414151007.Horde.J64vHh1YCZnRSzK17hZ84sB@webmail.kiener-muenchen.de> (raw)
In-Reply-To: <91ca594b3f434040a54485339c0e320f@rohde-schwarz.com>


Hi Dave,

I just found this patch, which does not seem to be a correct solution  
to solve a race.
Maybe there is really an issue with the refcounting of data->kref, but  
currently I do
not have time to check this in home office.

At least I see a problem in usbtmc_probe()

After calling:
    /* Protect interrupt in endpoint data until iin_urb is freed */
    kref_get(&data->kref);
the refcounter is incremented again and if usbtmc_probe() fails, the  
counter is
only decremented with a single kref_put(..).

I don't know if this is the reason of Lv Yunglong's problem, but let  
me know if
you have time to track down this issue, and we will work on a correct  
and tested
patch.

Regards,

Guido


> -----Original Message-----
> From: Greg KH
> Sent: Tuesday, March 23, 2021 10:44 AM
> To: Lv Yunlong <lyl2019@mail.ustc.edu.cn>
> Cc: linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2] usb: Add a lock when freeing data in  
> usbtmc_disconnect
>
> On Tue, Mar 23, 2021 at 02:28:54AM -0700, Lv Yunlong wrote:
>> In usbtmc_disconnect, data is got from intf with the initial reference.
>> There is no refcount inc operation before usbmc_free_int(data). In
>> usbmc_free_int(data), the data may be freed.
>>
>> But later in usbtmc_disconnect, there is another put function of data.
>> It could cause errors in race.
>>
>> My patch adds a lock to protect kref from changing in race.
>>
>> Signed-off-by: Lv Yunlong <lyl2019@mail.ustc.edu.cn>
>> ---
>>  drivers/usb/class/usbtmc.c | 5 +++++
>>  1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/usb/class/usbtmc.c b/drivers/usb/class/usbtmc.c
>> index 74d5a9c5238a..44f1fcabbb1e 100644
>> --- a/drivers/usb/class/usbtmc.c
>> +++ b/drivers/usb/class/usbtmc.c
>> @@ -2493,8 +2493,13 @@ static void usbtmc_disconnect(struct  
>> usb_interface *intf)
>>  		usb_scuttle_anchored_urbs(&file_data->in_anchor);
>>  	}
>>  	mutex_unlock(&data->io_mutex);
>> +
>> +	spinlock_t *dev_lock = &data->dev_lock;
>> +
>> +	spin_lock_irq(dev_lock);
>>  	usbtmc_free_int(data);
>>  	kref_put(&data->kref, usbtmc_delete);
>> +	spin_unlock_irq(dev_lock);
>>  }
>>
>>  static void usbtmc_draw_down(struct usbtmc_file_data *file_data)
>> --
>> 2.25.1
>
> You obviously did not even build this patch, let alone test it :(
>
> Please do not waste maintainer's time by not doing the proper steps  
> when submitting patches.
>
> thanks,
>
> greg k-h




       reply	other threads:[~2021-04-14 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <91ca594b3f434040a54485339c0e320f@rohde-schwarz.com>
2021-04-14 15:10 ` guido [this message]
2021-03-23  9:28 [PATCH v2] usb: Add a lock when freeing data in usbtmc_disconnect Lv Yunlong
2021-03-23  9:44 ` Greg KH

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=20210414151007.Horde.J64vHh1YCZnRSzK17hZ84sB@webmail.kiener-muenchen.de \
    --to=guido@kiener-muenchen.de \
    --cc=dpenkler@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guido.kiener@rohde-schwarz.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=lyl2019@mail.ustc.edu.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.