[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <de8af03b-4948-47c4-b9f8-68f7e4112264@I-love.SAKURA.ne.jp>
Date: Thu, 3 Jul 2025 10:48:56 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: Hillf Danton <hdanton@...a.com>, Alan Stern <stern@...land.harvard.edu>,
Mark Brown <broonie@...nel.org>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: 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 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.
Powered by blists - more mailing lists