From: Matthew Wilcox <willy@infradead.org>
To: Kun Hu <huk23@m.fudan.edu.cn>
Cc: hch@lst.de, jlayton@kernel.org, kirill.shutemov@linux.intel.com,
vbabka@suse.cz, william.kucharski@oracle.com, rppt@linux.ibm.com,
dhowells@redhat.com, akpm@linux-foundation.org, hughd@google.com,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: Bug: task hung in shmem_swapin_folio
Date: Sun, 12 Jan 2025 12:02:09 +0000 [thread overview]
Message-ID: <Z4OvQfse4hekeD-A@casper.infradead.org> (raw)
In-Reply-To: <F5B70018-2D83-4EA8-9321-D260C62BF5E3@m.fudan.edu.cn>
On Sun, Jan 12, 2025 at 05:46:24PM +0800, Kun Hu wrote:
> Hello,
>
> When using our customized fuzzer tool to fuzz the latest Linux kernel, the following crash (42s)
> was triggered.
It's not a crash. It's a warning. You've just configured your kernel
to crash when emitting a warning.
What you need to do is poke around in the reproducer you've found and
figure out what it is you're doing that causes this warning. Are
you constraining your task with memory groups, for example? Are you
doing a huge amount of I/O which is causing your disk to be
bottlenecked? Something else?
It's all very well to automate finding bugs, but you're asking other
people to do a lot of the work for you.
next prev parent reply other threads:[~2025-01-12 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 9:46 Kun Hu
2025-01-12 12:02 ` Matthew Wilcox [this message]
2025-01-12 12:51 ` Kun Hu
2025-01-13 5:06 ` Matthew Wilcox
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=Z4OvQfse4hekeD-A@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=hughd@google.com \
--cc=huk23@m.fudan.edu.cn \
--cc=jlayton@kernel.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.com \
--cc=vbabka@suse.cz \
--cc=william.kucharski@oracle.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