Hello,
syzbot found the following issue on:
HEAD commit: 8e8fc038cad5 Linux 6.1.168
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1044f302580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=b1adc0bfde2d8a4a
dashboard link:
https://syzkaller.appspot.com/bug?extid=ede06bed98ae98f3b098
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/1821c80470d7/disk-8e8fc038.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/289636f01a54/vmlinux-8e8fc038.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/580462ce5f63/Image-8e8fc038.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+ede06b...@syzkaller.appspotmail.com
loop1: detected capacity change from 0 to 4096
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4537 at fs/nilfs2/sufile.c:475 nilfs_sufile_do_free+0x470/0x76c fs/nilfs2/sufile.c:475
Modules linked in:
CPU: 0 PID: 4537 Comm: syz.1.33 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/26/2026
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : nilfs_sufile_do_free+0x470/0x76c fs/nilfs2/sufile.c:475
lr : nilfs_sufile_do_free+0x470/0x76c fs/nilfs2/sufile.c:475
sp : ffff800021246fb0
x29: ffff800021246fe0 x28: dfff800000000000 x27: 0000000000008000
x26: ffff0000f51c30bc x25: ffff0000f51c30b0 x24: ffff0000e26225e8
x23: ffff0000ccb515d8 x22: 1fffe0001996a2bb x21: 0000000000008000
x20: 1fffe0001ea38617 x19: ffff0000ccb50000 x18: ffff800011b9bf60
x17: ffff80001835b000 x16: ffff8000082d7db8 x15: 0000000000000002
x14: 00000000ffffffef x13: 0000000000ff0100 x12: 0000000000080000
x11: 0000000000014637 x10: ffff800021afc000 x9 : ffff800009c91bdc
x8 : 0000000000014638 x7 : ffff8000086f2be4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff0000f88b9488
x2 : ffff0000f88b9488 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
nilfs_sufile_do_free+0x470/0x76c fs/nilfs2/sufile.c:475
nilfs_sufile_updatev+0x314/0x540 fs/nilfs2/sufile.c:196
nilfs_sufile_freev fs/nilfs2/sufile.h:87 [inline]
nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1246 [inline]
nilfs_segctor_collect fs/nilfs2/segment.c:1534 [inline]
nilfs_segctor_do_construct+0x19b4/0x61f8 fs/nilfs2/segment.c:2090
nilfs_segctor_construct+0x134/0x540 fs/nilfs2/segment.c:2453
nilfs_clean_segments+0x2e8/0x870 fs/nilfs2/segment.c:2527
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: 11862
hardirqs last enabled at (11861): [<ffff800011b238fc>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (11861): [<ffff800011b238fc>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (11862): [<ffff800011a387cc>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (11708): [<ffff800008030954>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (11706): [<ffff800008030920>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
---
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