From: Junjie Cao <junjie.cao@linux.dev>
To: syzbot+466a45fcfb0562f5b9a0@syzkaller.appspotmail.com,
Ryusuke Konishi <konishi.ryusuke@gmail.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Junjie Cao <junjie.cao@linux.dev>
Subject: Re: [syzbot] [nilfs?] WARNING in nilfs_ioctl_prepare_clean_segments
Date: Tue, 24 Mar 2026 19:26:41 +0800 [thread overview]
Message-ID: <f75eb907cfe0944a5cc3bd02d137fce8.junjie.cao@linux.dev> (raw)
In-Reply-To: <65f731a33b7f0f5e26bf288505694c9a.junjie.cao@linux.dev>
Please test this branch.
#syz test: https://github.com/Lukaaa525/linux-kernel.git nilfs2-mark-blocks-dirty-fix-syztest
next prev parent reply other threads:[~2026-03-24 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <69b8c9a9.a00a0220.3b25d1.002a.GAE@google.com>
2026-03-23 0:49 ` [syzbot] [nilfs?] WARNING in nilfs_ioctl_prepare_clean_segments syzbot
2026-03-24 10:45 ` Junjie Cao
2026-03-24 11:26 ` Junjie Cao [this message]
2026-03-24 12:01 ` syzbot
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=f75eb907cfe0944a5cc3bd02d137fce8.junjie.cao@linux.dev \
--to=junjie.cao@linux.dev \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+466a45fcfb0562f5b9a0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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