From: Lu Baolu <baolu.lu@linux.intel.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
zhengjun.xing@linux.intel.com,
Guoqing Zhang <guoqing.zhang@intel.com>
Subject: Re: [PATCH v2 1/5] usb: xhci: Disable slot even virt-dev is null
Date: Fri, 11 Aug 2017 09:18:10 +0800 [thread overview]
Message-ID: <598D05D2.7040403@linux.intel.com> (raw)
In-Reply-To: <598C2EA4.7010803@linux.intel.com>
Hi,
On 08/10/2017 06:00 PM, Mathias Nyman wrote:
> On 10.08.2017 03:35, Lu Baolu wrote:
>> Hi,
>>
>> On 08/09/2017 03:58 PM, Mathias Nyman wrote:
>>> On 27.07.2017 05:21, Lu Baolu wrote:
>>>> xhci_disable_slot() is a helper for disabling a slot when a device
>>>> goes away or recovers from error situations. Currently, it checks
>>>> the corespoding virt-dev pointer and returns directly (w/o issuing
>>>> disable slot command) if it's null.
>>>>
>>>> This is unnecessary and will cause problems in case where virt-dev
>>>> allocation fails and xhci_disable_slot() is called to roll back the
>>>> hardware state. Refer to the implementation of xhci_alloc_dev().
>>>>
>>>
>>> True, checking for xhci->devs[slot_id] doesn't work if xhci_alloc_dev()
>>> failed xhci_alloc_virt_device() and calls xhci_disable_slot,
>>>
>>> but the virt dev check is needed for test mode, which will just try
>>> to disable all slots from 1 to HCS_MAX_SLOTS:
>>>
>>> xhci_enter_test_mode(..)
>>> /* Disable all Device Slots */
>>> for (i = 1; i <= HCS_MAX_SLOTS(xhci->hcs_params1); i++) {
>>> retval = xhci_disable_slot(xhci, NULL, i);
>>>
>>>
>>
>> So, how about checking virt dev before this invoking?
>>
>> @@ -612,10 +612,12 @@ static int xhci_enter_test_mode(struct xhci_hcd *xhci,
>> xhci_dbg(xhci, "Disable all slots\n");
>> spin_unlock_irqrestore(&xhci->lock, *flags);
>> for (i = 1; i <= HCS_MAX_SLOTS(xhci->hcs_params1); i++) {
>> - retval = xhci_disable_slot(xhci, NULL, i);
>> - if (retval)
>> - xhci_err(xhci, "Failed to disable slot %d, %d. Enter test mode anyway\n",
>> - i, retval);
>> + if (xhci->devs[i]) {
>> + retval = xhci_disable_slot(xhci, NULL, i);
>> + if (retval)
>> + xhci_err(xhci, "Failed to disable slot %d, %d. Enter test mode anyway\n",
>> + i, retval);
>> + }
>
>
> Yes, something like this will work
>
Okay, I will submit a v3 to include this change.
Best regards,
Lu Baolu
next prev parent reply other threads:[~2017-08-11 1:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 2:21 [PATCH v2 0/5] usb: xhci: Handle USB transaction error on address command Lu Baolu
2017-07-27 2:21 ` [PATCH v2 1/5] usb: xhci: Disable slot even virt-dev is null Lu Baolu
2017-08-09 7:58 ` Mathias Nyman
2017-08-10 0:35 ` Lu Baolu
2017-08-10 10:00 ` Mathias Nyman
2017-08-11 1:18 ` Lu Baolu [this message]
2017-07-27 2:21 ` [PATCH v2 2/5] usb: xhci: Fix potential memory leak in xhci_disable_slot() Lu Baolu
2017-08-09 10:09 ` Mathias Nyman
2017-07-27 2:21 ` [PATCH v2 3/5] usb: xhci: Fix memory leak when xhci_disable_slot() returns error Lu Baolu
2017-07-27 2:21 ` [PATCH v2 4/5] usb: xhci: Return error when host is dead in xhci_disable_slot() Lu Baolu
2017-07-27 2:21 ` [PATCH v2 5/5] usb: xhci: Handle USB transaction error on address command Lu Baolu
2017-07-27 7:55 ` Felipe Balbi
2017-07-27 8:56 ` Lu Baolu
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=598D05D2.7040403@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=guoqing.zhang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=zhengjun.xing@linux.intel.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).