From: Matthew Wilcox <willy@infradead.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Jan Kara <jack@suse.cz>, Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Luka <luka.2016.cs@gmail.com>
Subject: Re: [Bug] possible deadlock in vfs_rmdir in Linux kernel v6.12
Date: Wed, 4 Jun 2025 21:39:20 +0100 [thread overview]
Message-ID: <aECu-D3Df28hYI9L@casper.infradead.org> (raw)
In-Reply-To: <20250604-daft-nondescript-junglefowl-0abd5a@lemur>
On Wed, Jun 04, 2025 at 04:11:21PM -0400, Konstantin Ryabitsev wrote:
> Yes, hence my question. I think it's just a bad medium. It's actually the kind
> of thing that bugzilla is okay to use for -- create a bug with attachments and
> report it to the list, so maybe the original author can use that instead of
> pastebin sites?
The "author" looks to be a bot, frankly. At best yet-another-incompetent
user of "my modified version of syzkaller". There's no signal here,
would recommend just banning.
next prev parent reply other threads:[~2025-06-04 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 4:38 [Bug] possible deadlock in vfs_rmdir in Linux kernel v6.12 Luka
2025-06-04 4:21 ` [Bug] kernel BUG in may_delete in linux " Luka
2025-06-04 4:12 ` [BUG] task hung in fs_bdev_sync in linux v6.12 Luka
2025-06-04 7:45 ` [Bug] possible deadlock in vfs_rmdir in Linux kernel v6.12 Christian Brauner
2025-06-04 14:45 ` Konstantin Ryabitsev
2025-06-04 15:44 ` Jan Kara
2025-06-04 20:11 ` Konstantin Ryabitsev
2025-06-04 20:39 ` Matthew Wilcox [this message]
2025-06-04 21:11 ` Al Viro
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=aECu-D3Df28hYI9L@casper.infradead.org \
--to=willy@infradead.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=konstantin@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.2016.cs@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).