From: Christian Brauner <brauner@kernel.org>
To: Kun Hu <huk23@m.fudan.edu.cn>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
jack@suse.cz
Cc: jlayton@redhat.com, tytso@mit.edu, adilger.kernel@dilger.ca,
david@fromorbit.com, bfields@redhat.com,
viro@zeniv.linux.org.uk, christian.brauner@ubuntu.com,
hch@lst.de, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Bug: INFO_ task hung in lock_two_nondirectories
Date: Mon, 13 Jan 2025 15:38:57 +0100 [thread overview]
Message-ID: <20250113-herzhaft-desolat-e4d191b82bdf@brauner> (raw)
In-Reply-To: <42BD15B5-3C6C-437E-BF52-E22E6F200513@m.fudan.edu.cn>
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.
next prev parent reply other threads:[~2025-01-13 14:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 10:00 Bug: INFO_ task hung in lock_two_nondirectories Kun Hu
2025-01-13 10:28 ` Jan Kara
2025-01-13 20:00 ` Kent Overstreet
2025-01-14 9:07 ` Dmitry Vyukov
2025-01-14 9:20 ` Kun Hu
2025-01-14 13:57 ` Theodore Ts'o
2025-01-14 21:21 ` Dave Chinner
2025-01-14 23:23 ` Darrick J. Wong
2025-01-15 0:38 ` Kent Overstreet
2025-01-14 13:58 ` Jan Kara
2025-01-14 15:39 ` James Bottomley
[not found] ` <D067012D-7E8D-4AD9-A0CA-66B397110989@m.fudan.edu.cn>
2025-01-14 15:09 ` Kent Overstreet
2025-01-16 9:37 ` Kun Hu
2025-01-16 14:12 ` Kent Overstreet
2025-01-24 12:22 ` Kun Hu
2025-01-24 14:15 ` Kent Overstreet
2025-01-24 18:28 ` Theodore Ts'o
2025-01-24 18:39 ` Kent Overstreet
2025-01-14 9:27 ` Kun Hu
2025-01-14 2:54 ` Kun Hu
2025-01-13 14:38 ` Christian Brauner [this message]
2025-01-13 16:19 ` Matthew Wilcox
2025-01-13 18:08 ` Darrick J. Wong
2025-01-14 8:59 ` Dmitry Vyukov
2025-01-14 23:42 ` Darrick J. Wong
2025-01-14 9:15 ` Dmitry Vyukov
2025-01-14 23:43 ` Darrick J. Wong
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=20250113-herzhaft-desolat-e4d191b82bdf@brauner \
--to=brauner@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=andreyknvl@gmail.com \
--cc=bfields@redhat.com \
--cc=christian.brauner@ubuntu.com \
--cc=david@fromorbit.com \
--cc=dvyukov@google.com \
--cc=hch@lst.de \
--cc=huk23@m.fudan.edu.cn \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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