linux-kernel - Re: [Syzkaller & bisect] There is INFO: task hung in __rq_qos

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: <kuvbuekbzs6saggfxleiaqtl5mleozqozpamivz2zo6pd4istq@c6hfl6govn44>
Date: Wed, 23 Oct 2024 21:57:53 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: "Lai, Yi" <yi1.lai@...ux.intel.com>
Cc: linux-bcachefs@...r.kernel.org, linux-kernel@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: Re: [Syzkaller & bisect] There is INFO: task hung in
 __rq_qos_throttle

On Mon, Oct 21, 2024 at 06:27:25PM +0800, Lai, Yi wrote:
> Hi Kent Overstreet,
> 
> Greetings!
> 
> I used Syzkaller and found that there is INFO: task hung in __rq_qos_throttle in v6.12-rc2
> 
> After bisection and the first bad commit is:
> "
> 63332394c7e1 bcachefs: Move snapshot table size to struct snapshot_table

You sure...?

Look at the patch, that's a pretty unlikely culprit; we would've seen
something from kasan, and anyways there's guards on the new memory
accesses/array derefs.

I've been seeing that bug too, but it's very intermittent. How did you
get it to trigger reliably enough for a bisect?