From: syzbot <syzbot+466a45fcfb0562f5b9a0@syzkaller.appspotmail.com>
To: junjie.cao@linux.dev, konishi.ryusuke@gmail.com,
linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org,
slava@dubeyko.com, stable@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nilfs?] WARNING in nilfs_ioctl_prepare_clean_segments
Date: Tue, 24 Mar 2026 05:01:02 -0700 [thread overview]
Message-ID: <69c27cfe.a70a0220.59f55.0006.GAE@google.com> (raw)
In-Reply-To: <f75eb907cfe0944a5cc3bd02d137fce8.junjie.cao@linux.dev>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+466a45fcfb0562f5b9a0@syzkaller.appspotmail.com
Tested-by: syzbot+466a45fcfb0562f5b9a0@syzkaller.appspotmail.com
Tested on:
commit: ebd34541 nilfs2: skip blocks with no bmap entry in nil..
git tree: https://github.com/Lukaaa525/linux-kernel.git nilfs2-mark-blocks-dirty-fix-syztest
console output: https://syzkaller.appspot.com/x/log.txt?x=1100d6da580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a1eff8566a28238e
dashboard link: https://syzkaller.appspot.com/bug?extid=466a45fcfb0562f5b9a0
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2026-03-24 12:01 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
2026-03-24 12:01 ` syzbot [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=69c27cfe.a70a0220.59f55.0006.GAE@google.com \
--to=syzbot+466a45fcfb0562f5b9a0@syzkaller.appspotmail.com \
--cc=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=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