From: syzbot <syzbot+98a040252119df0506f8@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, kartikey406@gmail.com,
konishi.ryusuke@gmail.com, linux-kernel@vger.kernel.org,
linux-nilfs@vger.kernel.org, sato.koji@lab.ntt.co.jp,
slava@dubeyko.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nilfs?] WARNING in nilfs_btree_mark
Date: Sun, 22 Mar 2026 10:35:23 -0700 [thread overview]
Message-ID: <69c0285b.050a0220.3bf4de.0087.GAE@google.com> (raw)
In-Reply-To: <69bba3ff.050a0220.227207.0031.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 113ae7b4decc Merge tag 'hwmon-for-v7.0-rc5' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16f841d6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6754c86e8d9e4c91
dashboard link: https://syzkaller.appspot.com/bug?extid=98a040252119df0506f8
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10a52cba580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14108b52580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4905694a5f6d/disk-113ae7b4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/70f903690e79/vmlinux-113ae7b4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f3b857f0e5b8/bzImage-113ae7b4.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/89bbedcc6080/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+98a040252119df0506f8@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 4096
------------[ cut here ]------------
ret == -ENOENT
WARNING: fs/nilfs2/btree.c:2356 at nilfs_btree_mark+0x1c9/0x210 fs/nilfs2/btree.c:2356, CPU#1: syz.0.17/5978
Modules linked in:
CPU: 1 UID: 0 PID: 5978 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:nilfs_btree_mark+0x1c9/0x210 fs/nilfs2/btree.c:2356
Code: 48 8b 05 fa 0d 70 0f 48 3b 44 24 10 75 26 89 e8 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d e9 c9 1e 64 fd cc e8 b8 7e 19 fe 90 <0f> 0b 90 bd fe ff ff ff eb c3 e8 08 7f 02 08 44 89 f1 80 e1 07 80
RSP: 0018:ffffc900038075b0 EFLAGS: 00010293
RAX: ffffffff83ac2248 RBX: ffff888035117080 RCX: ffff888028170000
RDX: 0000000000000000 RSI: 00000000fffffffe RDI: 00000000fffffffe
RBP: 00000000fffffffe R08: 0000000000000341 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed1006a22ee3 R12: ffff88805726c5c0
R13: dffffc0000000000 R14: ffff88805726c588 R15: fffffffffffffff8
FS: 000055558815d500(0000) GS:ffff88812555d000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f663fff CR3: 00000000270a5000 CR4: 0000000000350ef0
Call Trace:
<TASK>
nilfs_bmap_mark+0xba/0x180 fs/nilfs2/bmap.c:402
nilfs_ioctl_mark_blocks_dirty fs/nilfs2/ioctl.c:764 [inline]
nilfs_ioctl_prepare_clean_segments+0x49a/0x800 fs/nilfs2/ioctl.c:799
nilfs_clean_segments+0x18c/0xa50 fs/nilfs2/segment.c:2525
nilfs_ioctl_clean_segments fs/nilfs2/ioctl.c:916 [inline]
nilfs_ioctl+0x261f/0x2780 fs/nilfs2/ioctl.c:1346
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f97fcd9c799
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fffdfc45fe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f97fd015fa0 RCX: 00007f97fcd9c799
RDX: 0000200000000640 RSI: 0000000040786e88 RDI: 0000000000000004
RBP: 00007f97fce32c99 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f97fd015fac R14: 00007f97fd015fa0 R15: 00007f97fd015fa0
</TASK>
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
next prev parent reply other threads:[~2026-03-22 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 7:21 [syzbot] [nilfs?] WARNING in nilfs_btree_mark syzbot
2026-03-19 7:58 ` Forwarded: [PATCH] nilfs2: fix missing continue after -ENOENT in nilfs_ioctl_mark_blocks_dirty() syzbot
2026-03-19 8:25 ` syzbot
2026-03-19 8:49 ` syzbot
2026-03-20 6:25 ` syzbot
2026-03-22 17:35 ` syzbot [this message]
[not found] <20260319075845.1086450-1-kartikey406@gmail.com>
2026-03-19 8:18 ` [syzbot] [nilfs?] WARNING in nilfs_btree_mark syzbot
[not found] <20260319082524.1087090-1-kartikey406@gmail.com>
2026-03-19 8:49 ` syzbot
[not found] <20260319084944.1088131-1-kartikey406@gmail.com>
2026-03-19 9:08 ` syzbot
[not found] <20260320062515.1098080-1-kartikey406@gmail.com>
2026-03-20 6:44 ` 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=69c0285b.050a0220.3bf4de.0087.GAE@google.com \
--to=syzbot+98a040252119df0506f8@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=kartikey406@gmail.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=sato.koji@lab.ntt.co.jp \
--cc=slava@dubeyko.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