Date:   Tue, 4 Jan 2022 16:00:30 -0500
From:   "Theodore Ts'o" <tytso@mit.edu>
To:     Matthew Wilcox <willy@infradead.org>
Cc:     kvartet <xyru1999@gmail.com>,
        Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
        sunhao.th@gmail.com
Subject: Re: INFO: task hung in __filemap_get_folio
Message-ID: <YdS1bk5txXiJynXV@mit.edu>
References: <CAFkrUsjD2HSRHdZ9yKANa0pLe8rhwPXKbU+E-A7K+td3jS5ZVA@mail.gmail.com>
 <YdSPb5Q6HytIi6w9@casper.infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YdSPb5Q6HytIi6w9@casper.infradead.org>
Precedence: bulk

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