Hello, syzbot found the following issue on: HEAD commit: aaa11ce2ffc8 Add linux-next specific files for 20220923 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=17870cdf080000 kernel config: https://syzkaller.appspot.com/x/.config?x=186d1ff305f10294 dashboard link: https://syzkaller.appspot.com/bug?extid=fbb3e0b24e8dae5a16ee compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 Unfortunately, I don't have any reproducer for this issue yet. IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+fbb3e0b24e8dae5a16ee@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 1 PID: 3320 at fs/nilfs2/segment.c:879 nilfs_segctor_create_checkpoint fs/nilfs2/segment.c:879 [inline] WARNING: CPU: 1 PID: 3320 at fs/nilfs2/segment.c:879 nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1197 [inline] WARNING: CPU: 1 PID: 3320 at fs/nilfs2/segment.c:879 nilfs_segctor_collect fs/nilfs2/segment.c:1497 [inline] WARNING: CPU: 1 PID: 3320 at fs/nilfs2/segment.c:879 nilfs_segctor_do_construct+0x45ac/0x69b0 fs/nilfs2/segment.c:2039 Modules linked in: CPU: 1 PID: 3320 Comm: segctord Not tainted 6.0.0-rc6-next-20220923-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022 RIP: 0010:nilfs_segctor_create_checkpoint fs/nilfs2/segment.c:879 [inline] RIP: 0010:nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1197 [inline] RIP: 0010:nilfs_segctor_collect fs/nilfs2/segment.c:1497 [inline] RIP: 0010:nilfs_segctor_do_construct+0x45ac/0x69b0 fs/nilfs2/segment.c:2039 Code: ff ff e8 27 7b 55 fe 41 83 fc ea 74 18 e8 4c 7e 55 fe 44 89 e6 bf fe ff ff ff e8 0f 7b 55 fe 41 83 fc fe 75 07 e8 34 7e 55 fe <0f> 0b e8 2d 7e 55 fe e9 3c de ff ff e8 23 7e 55 fe 48 8b 44 24 30 RSP: 0018:ffffc9000b897b40 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff888030627000 RCX: 0000000000000000 RDX: ffff88802da60000 RSI: ffffffff832715cc RDI: 0000000000000005 RBP: ffff8880306272d0 R08: 0000000000000005 R09: 00000000fffffffe R10: 00000000fffffffe R11: 0000000000000001 R12: 00000000fffffffe R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888021df8800 FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f8bbee45fc8 CR3: 0000000032ce7000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 000000000000003b DR6: 00000000ffff0ff0 DR7: 0000000000000400 Call Trace: <TASK> nilfs_segctor_construct+0x8e3/0xb30 fs/nilfs2/segment.c:2373 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2481 [inline] nilfs_segctor_thread+0x3c3/0xf30 fs/nilfs2/segment.c:2564 kthread+0x2e4/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 </TASK> --- 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 syzkaller@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
