From: Christian Brauner <brauner@kernel.org>
To: syzbot <syzbot+5b9d613904b2f185f2fe@syzkaller.appspotmail.com>
Cc: jack@suse.cz, jfs-discussion@lists.sourceforge.net,
konishi.ryusuke@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org,
shaggy@kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [jfs?] [nilfs?] WARNING in mnt_ns_release
Date: Sat, 4 Jan 2025 10:11:19 +0100 [thread overview]
Message-ID: <20250104-vokabel-nimmersatt-8534deaf69ff@brauner> (raw)
In-Reply-To: <677030ff.050a0220.2f3838.0499.GAE@google.com>
On Sat, Dec 28, 2024 at 09:10:23AM -0800, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 8155b4ef3466 Add linux-next specific files for 20241220
This is already fixed in -next. Please report if this happens again.
prev parent reply other threads:[~2025-01-04 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 4:48 [syzbot] [jfs?] [nilfs?] WARNING in mnt_ns_release syzbot
2024-12-28 17:10 ` syzbot
2025-01-04 9:11 ` Christian Brauner [this message]
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=20250104-vokabel-nimmersatt-8534deaf69ff@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzbot+5b9d613904b2f185f2fe@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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