[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250113-herzhaft-desolat-e4d191b82bdf@brauner>
Date: Mon, 13 Jan 2025 15:38:57 +0100
From: Christian Brauner <brauner@...nel.org>
To: Kun Hu <huk23@...udan.edu.cn>, Andrey Konovalov <andreyknvl@...il.com>,
Dmitry Vyukov <dvyukov@...gle.com>, jack@...e.cz
Cc: jlayton@...hat.com, tytso@....edu, adilger.kernel@...ger.ca,
david@...morbit.com, bfields@...hat.com, viro@...iv.linux.org.uk,
christian.brauner@...ntu.com, hch@....de, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: Bug: INFO_ task hung in lock_two_nondirectories
On Sun, Jan 12, 2025 at 06:00:24PM +0800, Kun Hu wrote:
> Hello,
>
> When using our customized fuzzer tool to fuzz the latest Linux kernel, the following crash (43s)
> was triggered.
I think we need to come to an agreement at LSFMM or somewhere else that
we will by default ingore but reports from non-syzbot fuzzers. Because
we're all wasting time on them.
Powered by blists - more mailing lists