Date:   Tue, 4 Jan 2022 18:18:23 +0000
From:   Matthew Wilcox <willy@infradead.org>
To:     kvartet <xyru1999@gmail.com>
Cc:     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: <YdSPb5Q6HytIi6w9@casper.infradead.org>
References: <CAFkrUsjD2HSRHdZ9yKANa0pLe8rhwPXKbU+E-A7K+td3jS5ZVA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAFkrUsjD2HSRHdZ9yKANa0pLe8rhwPXKbU+E-A7K+td3jS5ZVA@mail.gmail.com>
Precedence: bulk

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.