[v6.1] WARNING in nilfs_ioctl_prepare_clean_segments

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7c87defbd336 Linux 6.1.169
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1641acce580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b1adc0bfde2d8a4a
dashboard link: https://syzkaller.appspot.com/bug?extid=509f05b180eba6a0348b
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cf55a056d548/disk-7c87defb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/af13139876bb/vmlinux-7c87defb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/02c231cd5348/Image-7c87defb.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+509f05...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 4927 at fs/nilfs2/ioctl.c:772 nilfs_ioctl_mark_blocks_dirty fs/nilfs2/ioctl.c:772 [inline]
WARNING: CPU: 1 PID: 4927 at fs/nilfs2/ioctl.c:772 nilfs_ioctl_prepare_clean_segments+0x724/0x730 fs/nilfs2/ioctl.c:814
Modules linked in:
CPU: 1 PID: 4927 Comm: syz.3.114 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : nilfs_ioctl_mark_blocks_dirty fs/nilfs2/ioctl.c:772 [inline]
pc : nilfs_ioctl_prepare_clean_segments+0x724/0x730 fs/nilfs2/ioctl.c:814
lr : nilfs_ioctl_mark_blocks_dirty fs/nilfs2/ioctl.c:772 [inline]
lr : nilfs_ioctl_prepare_clean_segments+0x724/0x730 fs/nilfs2/ioctl.c:814
sp : ffff800021887600
x29: ffff8000218876a0 x28: dfff800000000000 x27: 0000000000000000

x26: ffff8000207021b0
x25: ffff8000207021a8 x24: 00000000fffffffe
x23: 1ffff000040e0435 x22: 1ffff000040e0434 x21: ffff800020702190
x20: ffff0000db6942c8 x19: 000000000000000b x18: 0000000000000000
x17: ffff80001835b000 x16: ffff8000082d92bc x15: 0000000000000002
x14: 00000000fffffffe x13: 0000000000ff0100 x12: 0000000000080000
x11: 000000000000f2a9 x10: ffff800025b5b000 x9 : ffff800009c9d1cc
x8 : 000000000000f2aa x7 : ffff80000805983c x6 : ffff800008059a4c
x5 : ffff0000df7e1568 x4 : ffff800021886f20 x3 : ffff800008a90cc0
x2 : 0000000000000001 x1 : ffff800015880cb0 x0 : 00000000fffffffe
Call trace:
nilfs_ioctl_mark_blocks_dirty fs/nilfs2/ioctl.c:772 [inline]
nilfs_ioctl_prepare_clean_segments+0x724/0x730 fs/nilfs2/ioctl.c:814
nilfs_clean_segments+0x148/0x870 fs/nilfs2/segment.c:2516
nilfs_ioctl_clean_segments fs/nilfs2/ioctl.c:940 [inline]
nilfs_ioctl+0x22c0/0x2660 fs/nilfs2/ioctl.c:1304
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl fs/ioctl.c:856 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 12686
hardirqs last enabled at (12685): [<ffff8000088e8344>] kasan_quarantine_put+0xc4/0x200 mm/kasan/quarantine.c:242
hardirqs last disabled at (12686): [<ffff800011a38ccc>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (12530): [<ffff800008030954>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (12528): [<ffff800008030920>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
NILFS (loop3): error -2 preparing GC: cannot mark copying blocks dirty


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 7c87defbd336 Linux 6.1.169
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=175aac36580000

kernel config: https://syzkaller.appspot.com/x/.config?x=b1adc0bfde2d8a4a
dashboard link: https://syzkaller.appspot.com/bug?extid=509f05b180eba6a0348b
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=111b5906580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e074ce580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cf55a056d548/disk-7c87defb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/af13139876bb/vmlinux-7c87defb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/02c231cd5348/Image-7c87defb.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/f84a6e832f54/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+509f05...@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 4096
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4451 at fs/nilfs2/ioctl.c:772 nilfs_ioctl_mark_blocks_dirty fs/nilfs2/ioctl.c:772 [inline]
WARNING: CPU: 0 PID: 4451 at fs/nilfs2/ioctl.c:772 nilfs_ioctl_prepare_clean_segments+0x724/0x730 fs/nilfs2/ioctl.c:814
Modules linked in:
CPU: 0 PID: 4451 Comm: syz.0.17 Not tainted syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : nilfs_ioctl_mark_blocks_dirty fs/nilfs2/ioctl.c:772 [inline]
pc : nilfs_ioctl_prepare_clean_segments+0x724/0x730 fs/nilfs2/ioctl.c:814
lr : nilfs_ioctl_mark_blocks_dirty fs/nilfs2/ioctl.c:772 [inline]
lr : nilfs_ioctl_prepare_clean_segments+0x724/0x730 fs/nilfs2/ioctl.c:814

sp : ffff800020cc7600
x29: ffff800020cc76a0 x28: dfff800000000000 x27: 0000000000000000
x26: ffff8000207ff1b0 x25: ffff8000207ff1a8 x24: 00000000fffffffe
x23: 1ffff000040ffe35 x22: 1ffff000040ffe34 x21: ffff8000207ff190
x20: ffff0000d3be62c8 x19: 000000000000000b x18: 0000000000000000
x17: ffff80001835b000 x16: ffff8000082d92bc x15: 0000000000000000
x14: 00000000fffffffe x13: 0000000000ff0100 x12: 0000000000ff0100
x11: ff00800009c9d1cc x10: 0000000000000000 x9 : ffff800009c9d1cc
x8 : ffff0000d4138000 x7 : ffff80000805983c x6 : ffff800008059a4c
x5 : ffff0000dbc3d4e8 x4 : ffff800020cc6f20 x3 : ffff800008a90cc0

x2 : 0000000000000001 x1 : ffff800015880cb0 x0 : 00000000fffffffe
Call trace:
nilfs_ioctl_mark_blocks_dirty fs/nilfs2/ioctl.c:772 [inline]
nilfs_ioctl_prepare_clean_segments+0x724/0x730 fs/nilfs2/ioctl.c:814
nilfs_clean_segments+0x148/0x870 fs/nilfs2/segment.c:2516
nilfs_ioctl_clean_segments fs/nilfs2/ioctl.c:940 [inline]
nilfs_ioctl+0x22c0/0x2660 fs/nilfs2/ioctl.c:1304
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl fs/ioctl.c:856 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

irq event stamp: 13536
hardirqs last enabled at (13535): [<ffff8000088e8344>] kasan_quarantine_put+0xc4/0x200 mm/kasan/quarantine.c:242
hardirqs last disabled at (13536): [<ffff800011a38ccc>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (13408): [<ffff800008030954>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (13406): [<ffff800008030920>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19

---[ end trace 0000000000000000 ]---

NILFS (loop0): error -2 preparing GC: cannot mark copying blocks dirty


---
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.