linux-kernel - Re: [syzbot] [usb?] INFO: rcu detected stall in schedule

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <3e1b188f-2a68-461c-9b7c-a1d85bf8eb31@rowland.harvard.edu>
Date: Tue, 4 Jun 2024 10:20:31 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: Marcello Sylvester Bauer <marcello.bauer@...ements.com>
Cc: syzbot <syzbot+c793a7eca38803212c61@...kaller.appspotmail.com>,
  bp@...en8.de, dave.hansen@...ux.intel.com, gregkh@...uxfoundation.org,
  hpa@...or.com, linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
  mingo@...hat.com, syzkaller-bugs@...glegroups.com, tglx@...utronix.de,
  x86@...nel.org, Matthias Stoeckl <matthias.stoeckl@...unet.com>,
  Uwe Kleine-Koenig <u.kleine-koenig@...gutronix.de>
Subject: Re: [syzbot] [usb?] INFO: rcu detected stall in schedule_timeout (6)

On Tue, Jun 04, 2024 at 02:05:12PM +0200, Marcello Sylvester Bauer wrote:
> Greetings,
> 
> I'm currently investigating this regression to properly fix it. My
> patch only replaces the corresponding timer API calls without actually
> changing the code. I'm trying to get it to work properly with the
> hrtimer API.
> 
> Any hints on how to accomplish this are welcome.

Start by figuring out what isn't getting executed.  That is, which USB 
(or usb_request) transfer isn't completing.  Once you know that, see 
what timer callbacks do occur (if any) and figure out why they don't 
cause the transfer to complete.

If there are no timer callbacks at all when the hang occurs, make a 
record (printk if nothing else), from the start of the test, of each 
callback and each timer restart, so you can definitively prove to the 
hrtimer maintainers that there's a restart with no later callback.  Then 
it will be up to them to figure out what's going wrong.

Alan Stern