linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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
Date: Tue, 4 Jan 2022 16:00:30 -0500	[thread overview]
Message-ID: <YdS1bk5txXiJynXV@mit.edu> (raw)
In-Reply-To: <YdSPb5Q6HytIi6w9@casper.infradead.org>

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


      reply	other threads:[~2022-01-04 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 11:44 INFO: task hung in __filemap_get_folio kvartet
2022-01-04 18:18 ` Matthew Wilcox
2022-01-04 21:00   ` Theodore Ts'o [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YdS1bk5txXiJynXV@mit.edu \
    --to=tytso@mit.edu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sunhao.th@gmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=willy@infradead.org \
    --cc=xyru1999@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).