[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b1657fab-b34f-4f52-94e7-333577cdb450@rowland.harvard.edu>
Date: Thu, 3 Jul 2025 17:27:39 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc: Hillf Danton <hdanton@...a.com>, Mark Brown <broonie@...nel.org>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
syzbot <syzbot+d630bd89141124cc543e@...kaller.appspotmail.com>,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
Boqun Feng <boqun.feng@...il.com>, linux-usb@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [usb?] INFO: task hung in hub_activate (3)
On Thu, Jul 03, 2025 at 10:48:56AM +0900, Tetsuo Handa wrote:
> On 2025/07/03 10:20, Tetsuo Handa wrote:
> > Caused by commit 9bd9c8026341 ("usb: hub: Fix flushing of delayed work
> > used for post resume purposes") with cc: stable.
> > Shouldn't we revert that commit and seek for a different approach
> > than wait for a reproducer?
> >
>
> Sorry, wrong commit.
>
> The line was added by commit a49e1e2e785f ("usb: hub: Fix flushing and
> scheduling of delayed work that tunes runtime pm") with cc: stable.
Mathias has posted a fix for this problem:
https://lore.kernel.org/linux-usb/20250627164348.3982628-2-mathias.nyman@linux.intel.com/
It hasn't gotten into Linus's tree yet.
Alan Stern
Powered by blists - more mailing lists