From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
oneukum@suse.com, stable@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
Subject: Re: [PATCH v2] usb: hub: fix detection of high tier USB3 devices behind suspended hubs
Date: Thu, 26 Jun 2025 15:18:29 +0300 [thread overview]
Message-ID: <85c7024d-69e0-4297-9a02-3afa2d2861f7@linux.intel.com> (raw)
In-Reply-To: <842ed535-ed0f-43d6-9b69-b5f9aeb853d2@oss.qualcomm.com>
On 25.6.2025 18.41, Konrad Dybcio wrote:
> On 6/25/25 5:11 PM, Mathias Nyman wrote:
>> On 24.6.2025 19.40, Konrad Dybcio wrote:
>>> On 6/24/25 11:47 AM, Mathias Nyman wrote:
>>>> On 23.6.2025 23.31, Konrad Dybcio wrote:
>>>>> On 6/11/25 1:24 PM, Mathias Nyman wrote:
>
> [...]
>
>> I added some memory debugging but wasn't able to trigger this.
>>
>> Does this oneliner help? It's a shot in the dark.
>>
>> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
>> index d41a6c239953..1cc853c428fc 100644
>> --- a/drivers/usb/core/hub.c
>> +++ b/drivers/usb/core/hub.c
>> @@ -1418,6 +1418,7 @@ static void hub_quiesce(struct usb_hub *hub, enum hub_quiescing_type type)
>>
>> /* Stop hub_wq and related activity */
>> timer_delete_sync(&hub->irq_urb_retry);
>> + flush_delayed_work(&hub->init_work);
>> usb_kill_urb(hub->urb);
>> if (hub->has_indicators)
>> cancel_delayed_work_sync(&hub->leds);
>
> I can't seem to trigger the bug anymore with this (and Alan's change)!
Thanks for testing
I'll send a proper patch that does these changes
-Mathias
prev parent reply other threads:[~2025-06-26 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 11:24 [PATCH v2] usb: hub: fix detection of high tier USB3 devices behind suspended hubs Mathias Nyman
2025-06-23 20:31 ` Konrad Dybcio
2025-06-23 23:32 ` Alan Stern
2025-06-24 9:49 ` Mathias Nyman
2025-06-24 9:47 ` Mathias Nyman
2025-06-24 16:40 ` Konrad Dybcio
2025-06-25 15:11 ` Mathias Nyman
2025-06-25 15:41 ` Konrad Dybcio
2025-06-26 12:18 ` Mathias Nyman [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=85c7024d-69e0-4297-9a02-3afa2d2861f7@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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