Re: [syzbot] [f2fs?] kernel BUG in new_curseg

[Chao Yu <chao@kernel.org>]

#syz test git://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip

On 2024/9/9 16:19, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    89f5e14d05b4 Merge tag 'timers_urgent_for_v6.11_rc7' of gi..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=14085f29980000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=58a85aa6925a8b78
> dashboard link: https://syzkaller.appspot.com/bug?extid=341e5f32ebafbb46b81c
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1614c807980000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13854e00580000
> 
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-89f5e14d.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/dfc310daee41/vmlinux-89f5e14d.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/a92f22c06568/bzImage-89f5e14d.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/c7aaf1741c93/mount_1.gz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+341e5f32ebafbb46b81c@syzkaller.appspotmail.com
> 
> F2FS-fs (loop0): inject no free segment in get_new_segment of __allocate_new_segment+0x1ce/0x940 fs/f2fs/segment.c:3167
> F2FS-fs (loop0): Stopped filesystem due to reason: 7
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/segment.c:2748!
> Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
> CPU: 0 UID: 0 PID: 5109 Comm: syz-executor304 Not tainted 6.11.0-rc6-syzkaller-00363-g89f5e14d05b4 #0
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
> RIP: 0010:get_new_segment fs/f2fs/segment.c:2748 [inline]
> RIP: 0010:new_curseg+0x1f61/0x1f70 fs/f2fs/segment.c:2836
> Code: 24 58 e8 12 b9 f2 ff eb 05 e8 4b 71 96 fd 48 8b 7c 24 70 e8 91 ac c6 07 48 8b 7c 24 10 31 f6 ba 07 00 00 00 e8 50 1e f6 ff 90 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 90 90 90 90 90 90 90
> RSP: 0018:ffffc9000179f548 EFLAGS: 00010246
> RAX: 8fb07c62f860e300 RBX: 00000000000002b2 RCX: 8fb07c62f860e300
> RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
> RBP: ffff8880125250c8 R08: ffffffff817401bc R09: 1ffff920002f3e20
> R10: dffffc0000000000 R11: fffff520002f3e21 R12: ffff8880008c2700
> R13: ffff8880125250cc R14: 1ffff110024a4a19 R15: 00000000000002b2
> FS:  0000555593e0e380(0000) GS:ffff88801fe00000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f6cf8cb40f8 CR3: 000000001255a000 CR4: 0000000000350ef0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
>   <TASK>
>   __allocate_new_segment+0x1ce/0x940 fs/f2fs/segment.c:3167
>   f2fs_allocate_new_section fs/f2fs/segment.c:3181 [inline]
>   f2fs_allocate_pinning_section+0xfa/0x4e0 fs/f2fs/segment.c:3195
>   f2fs_expand_inode_data+0x5d6/0xbb0 fs/f2fs/file.c:1799
>   f2fs_fallocate+0x448/0x960 fs/f2fs/file.c:1903
>   vfs_fallocate+0x553/0x6c0 fs/open.c:334
>   do_vfs_ioctl+0x2592/0x2e50 fs/ioctl.c:886
>   __do_sys_ioctl fs/ioctl.c:905 [inline]
>   __se_sys_ioctl+0x81/0x170 fs/ioctl.c:893
>   do_syscall_x64 arch/x86/entry/common.c:52 [inline]
>   do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
>   entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f6cf8c37229
> Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007ffeb5036b58 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
> RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007f6cf8c37229
> RDX: 00000000200000c0 RSI: 0000000040305828 RDI: 0000000000000004
> RBP: 0000000000000000 R08: 00007ffeb5036b90 R09: 00007ffeb5036b90
> R10: 00007ffeb5036b90 R11: 0000000000000246 R12: 00007ffeb5036b7c
> R13: 0000000000000002 R14: 431bde82d7b634db R15: 00007ffeb5036bb0
>   </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:get_new_segment fs/f2fs/segment.c:2748 [inline]
> RIP: 0010:new_curseg+0x1f61/0x1f70 fs/f2fs/segment.c:2836
> Code: 24 58 e8 12 b9 f2 ff eb 05 e8 4b 71 96 fd 48 8b 7c 24 70 e8 91 ac c6 07 48 8b 7c 24 10 31 f6 ba 07 00 00 00 e8 50 1e f6 ff 90 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 90 90 90 90 90 90 90
> RSP: 0018:ffffc9000179f548 EFLAGS: 00010246
> RAX: 8fb07c62f860e300 RBX: 00000000000002b2 RCX: 8fb07c62f860e300
> RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
> RBP: ffff8880125250c8 R08: ffffffff817401bc R09: 1ffff920002f3e20
> R10: dffffc0000000000 R11: fffff520002f3e21 R12: ffff8880008c2700
> R13: ffff8880125250cc R14: 1ffff110024a4a19 R15: 00000000000002b2
> FS:  0000555593e0e380(0000) GS:ffff88801fe00000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f6cf8cb40f8 CR3: 000000001255a000 CR4: 0000000000350ef0
> 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 syzkaller@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 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.
> 
> 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