lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <738a4a73-584c-4097-ab1b-156810f00c66@I-love.SAKURA.ne.jp>
Date: Fri, 4 Jul 2025 07:48:30 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: Alan Stern <stern@...land.harvard.edu>
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 2025/07/04 6:27, Alan Stern wrote:
> 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/

OK. No longer reproducing for 18 hours; assume already fixed.

#syz fix: usb: hub: Fix flushing of delayed work used for post resume purposes

> 
> It hasn't gotten into Linus's tree yet.

Since the cause commit is only in linux-next.git , it is no problem that
the fix commit is not yet in linux.git .

> 
> Alan Stern


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ