Hello,
syzbot found the following issue on:
HEAD commit: 91786f140358 Linux 5.15.175
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1555f5c4580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=1fc30776feb70ea7
dashboard link:
https://syzkaller.appspot.com/bug?extid=e0e7acee474d9914d580
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/210b1e4b59b1/disk-91786f14.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/1cf8391059a0/vmlinux-91786f14.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/1d9077a44b1c/bzImage-91786f14.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+e0e7ac...@syzkaller.appspotmail.com
F2FS-fs (loop1): Found nat_bits in checkpoint
F2FS-fs (loop1): Start checkpoint disabled!
F2FS-fs (loop1): Mounted with checkpoint version = 48b305e5
------------[ cut here ]------------
kernel BUG at fs/f2fs/segment.c:836!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 4345 Comm: syz.1.30 Not tainted 5.15.175-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__locate_dirty_segment+0xb53/0xb60 fs/f2fs/segment.c:835
Code: 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 2a fd ff ff 4c 89 e7 e8 0e 6f 1a fe e9 1d fd ff ff e8 f4 92 d0 fd 0f 0b e8 ed 92 d0 fd <0f> 0b e8 e6 92 d0 fd 0f 0b 0f 1f 40 00 55 41 57 41 56 41 55 41 54
RSP: 0018:ffffc9000327f1f0 EFLAGS: 00010283
RAX: ffffffff83aff1f3 RBX: ffff88805fec54f0 RCX: 0000000000080000
RDX: ffffc90005681000 RSI: 0000000000020bd5 RDI: 0000000000020bd6
RBP: 0000000000000000 R08: ffffffff83afec3f R09: ffffed102833bdaf
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888078ddba10
R13: 1ffff1100fa1d02d R14: 0000000000000002 R15: ffff88807d0e8168
FS: 00007f4f89ebc6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000001fb99000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
locate_dirty_segment+0x43f/0x5a0 fs/f2fs/segment.c:908
f2fs_invalidate_blocks+0x2b2/0x3a0 fs/f2fs/segment.c:2382
f2fs_truncate_data_blocks_range+0x79c/0xfe0 fs/f2fs/file.c:605
truncate_dnode fs/f2fs/node.c:943 [inline]
f2fs_truncate_inode_blocks+0xa3a/0x10d0 fs/f2fs/node.c:1155
f2fs_do_truncate_blocks+0x52e/0x9c0 fs/f2fs/file.c:723
f2fs_truncate_blocks+0x109/0x2f0 fs/f2fs/file.c:751
f2fs_truncate+0x3c2/0x740 fs/f2fs/file.c:803
f2fs_setattr+0xae3/0x11d0 fs/f2fs/file.c:974
notify_change+0xc6d/0xf50 fs/attr.c:505
do_truncate+0x21c/0x300 fs/open.c:65
handle_truncate fs/namei.c:3265 [inline]
do_open fs/namei.c:3612 [inline]
path_openat+0x28a3/0x2f20 fs/namei.c:3742
do_filp_open+0x21c/0x460 fs/namei.c:3769
do_sys_openat2+0x13b/0x4f0 fs/open.c:1253
do_sys_open fs/open.c:1269 [inline]
__do_sys_creat fs/open.c:1345 [inline]
__se_sys_creat fs/open.c:1339 [inline]
__x64_sys_creat+0x11f/0x160 fs/open.c:1339
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f4f8c04bd29
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4f89ebc038 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f4f8c23bfa0 RCX: 00007f4f8c04bd29
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000000
RBP: 00007f4f8c0c7b08 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f4f8c23bfa0 R15: 00007fff1f9d9368
</TASK>
Modules linked in:
---[ end trace 521da77abc80c21c ]---
RIP: 0010:__locate_dirty_segment+0xb53/0xb60 fs/f2fs/segment.c:835
Code: 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 2a fd ff ff 4c 89 e7 e8 0e 6f 1a fe e9 1d fd ff ff e8 f4 92 d0 fd 0f 0b e8 ed 92 d0 fd <0f> 0b e8 e6 92 d0 fd 0f 0b 0f 1f 40 00 55 41 57 41 56 41 55 41 54
RSP: 0018:ffffc9000327f1f0 EFLAGS: 00010283
RAX: ffffffff83aff1f3 RBX: ffff88805fec54f0 RCX: 0000000000080000
RDX: ffffc90005681000 RSI: 0000000000020bd5 RDI: 0000000000020bd6
RBP: 0000000000000000 R08: ffffffff83afec3f R09: ffffed102833bdaf
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888078ddba10
R13: 1ffff1100fa1d02d R14: 0000000000000002 R15: ffff88807d0e8168
FS: 00007f4f89ebc6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000001fb99000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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