[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z4OvQfse4hekeD-A@casper.infradead.org>
Date: Sun, 12 Jan 2025 12:02:09 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Kun Hu <huk23@...udan.edu.cn>
Cc: hch@....de, jlayton@...nel.org, kirill.shutemov@...ux.intel.com,
vbabka@...e.cz, william.kucharski@...cle.com, rppt@...ux.ibm.com,
dhowells@...hat.com, akpm@...ux-foundation.org, hughd@...gle.com,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: Bug: task hung in shmem_swapin_folio
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.
Powered by blists - more mailing lists