Hello,
syzbot found the following issue on:
HEAD commit: 8020ae3c051d Linux 5.15.103
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1080f131c80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=d4215fb4040f8f8d
dashboard link:
https://syzkaller.appspot.com/bug?extid=f95e0d2bc2dc67bc22bb
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/857e17de0f0a/disk-8020ae3c.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/9efc49fcd441/vmlinux-8020ae3c.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/f14c38b6bfa7/bzImage-8020ae3c.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+f95e0d...@syzkaller.appspotmail.com
NILFS (loop3): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3937 at fs/nilfs2/dat.c:193 nilfs_dat_commit_end+0x59c/0x6a0
Modules linked in:
CPU: 1 PID: 3937 Comm: segctord Not tainted 5.15.103-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:nilfs_dat_commit_end+0x59c/0x6a0 fs/nilfs2/dat.c:193
Code: 48 89 ee 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f 5d e9 d8 81 03 00 e8 13 b3 57 fe e8 3e c4 d7 fd e9 d8 fc ff ff e8 04 b3 57 fe <0f> 0b e9 39 fc ff ff e8 f8 b2 57 fe e8 23 c4 d7 fd 43 80 7c 35 00
RSP: 0018:ffffc9000538f2c8 EFLAGS: 00010293
RAX: ffffffff8328c5cc RBX: ffff888084a9b1a0 RCX: ffff88807529d700
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0001000000000002
RBP: 0000000000000003 R08: ffffffff8328c1fe R09: ffffed100f3e9c9b
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888075010180
R13: 1ffff92000a71e7b R14: 0001000000000002 R15: ffff88807529edb8
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005647bbe55e50 CR3: 000000007ced6000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
nilfs_dat_commit_update+0x25/0x40 fs/nilfs2/dat.c:243
nilfs_direct_propagate+0x23c/0x3b0 fs/nilfs2/direct.c:277
nilfs_bmap_propagate+0x6d/0x120 fs/nilfs2/bmap.c:337
nilfs_collect_file_data+0x49/0xc0 fs/nilfs2/segment.c:568
nilfs_segctor_apply_buffers+0x180/0x330 fs/nilfs2/segment.c:1018
nilfs_segctor_scan_file+0x82d/0xad0 fs/nilfs2/segment.c:1067
nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1197 [inline]
nilfs_segctor_collect fs/nilfs2/segment.c:1503 [inline]
nilfs_segctor_do_construct+0x1e63/0x7410 fs/nilfs2/segment.c:2045
nilfs_segctor_construct+0x145/0x8c0 fs/nilfs2/segment.c:2381
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2489 [inline]
nilfs_segctor_thread+0x54c/0x1140 fs/nilfs2/segment.c:2572
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.