linux-kernel - Re: INFO: task hung in __filemap_get

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]

Date:   Tue, 4 Jan 2022 16:00:30 -0500
From:   "Theodore Ts'o" <tytso@....edu>
To:     Matthew Wilcox <willy@...radead.org>
Cc:     kvartet <xyru1999@...il.com>,
        Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
        sunhao.th@...il.com
Subject: Re: INFO: task hung in __filemap_get_folio

On Tue, Jan 04, 2022 at 06:18:23PM +0000, Matthew Wilcox wrote:
> On Tue, Jan 04, 2022 at 07:44:10PM +0800, kvartet wrote:
> > Hello,
> > 
> > When using Syzkaller to fuzz the latest Linux kernel, the following
> > crash was triggered.
> 
> This isn't a crash, it's a notification of a hang.  More than likely
> syzbot is playing with RT scheduling again.
> 
> We do not need more people running syzbot.  We need more people tracking
> down and fixing the syzbot reports that already exist.

One of the syzbot spam reported by kvartet was a hang in the jbd2
layer, while it was waiting for processes to complete running handles,
and the oom killer lock was reported as being involved.  At which
point, I stopped reading or caring about *any* of the syzbot
complaints being reported by kvartet....

					- Ted