Hello, syzbot found the following issue on: HEAD commit: 555f3d7be91a Merge tag '5.17-rc3-ksmbd-server-fixes' of gi.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=11320c2c700000 kernel config: https://syzkaller.appspot.com/x/.config?x=266de9da75c71a45 dashboard link: https://syzkaller.appspot.com/bug?extid=9df2b537192e605d3f78 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+9df2b537192e605d3f78@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ kernel BUG at fs/ext4/extents.c:3199! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 0 PID: 14330 Comm: syz-executor.1 Not tainted 5.17.0-rc3-syzkaller-00020-g555f3d7be91a #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:ext4_split_extent_at+0x910/0xe10 fs/ext4/extents.c:3199 Code: de e8 74 52 6a ff 48 85 db 0f 84 37 04 00 00 e8 d6 4f 6a ff 66 41 81 ce 00 80 66 44 89 74 24 7c e9 0c fb ff ff e8 c0 4f 6a ff <0f> 0b e8 b9 4f 6a ff 4c 89 e8 31 ff 25 ff 7f 00 00 48 89 c6 48 89 RSP: 0018:ffffc9000476f730 EFLAGS: 00010212 RAX: 00000000000059b6 RBX: 0000000000008028 RCX: ffffc9000a282000 RDX: 0000000000040000 RSI: ffffffff820e28d0 RDI: 0000000000000003 RBP: ffff888072591c30 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff820e21c7 R11: 00000000ffff8000 R12: ffff88802603d054 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f8a3dd98700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b2d743000 CR3: 000000007dc31000 CR4: 0000000000350ef0 Call Trace: <TASK> ext4_force_split_extent_at fs/ext4/extents.c:319 [inline] ext4_swap_extents+0x8e3/0x14c0 fs/ext4/extents.c:5662 move_extent_per_page fs/ext4/move_extent.c:360 [inline] ext4_move_extents+0x1c86/0x3ee0 fs/ext4/move_extent.c:672 __ext4_ioctl+0x33e6/0x57e0 fs/ext4/ioctl.c:1285 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl fs/ioctl.c:860 [inline] __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f8a3f423059 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f8a3dd98168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f8a3f535f60 RCX: 00007f8a3f423059 RDX: 0000000020000200 RSI: 00000000c028660f RDI: 0000000000000005 RBP: 00007f8a3f47d08d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fffd2956f0f R14: 00007f8a3dd98300 R15: 0000000000022000 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:ext4_split_extent_at+0x910/0xe10 fs/ext4/extents.c:3199 Code: de e8 74 52 6a ff 48 85 db 0f 84 37 04 00 00 e8 d6 4f 6a ff 66 41 81 ce 00 80 66 44 89 74 24 7c e9 0c fb ff ff e8 c0 4f 6a ff <0f> 0b e8 b9 4f 6a ff 4c 89 e8 31 ff 25 ff 7f 00 00 48 89 c6 48 89 RSP: 0018:ffffc9000476f730 EFLAGS: 00010212 RAX: 00000000000059b6 RBX: 0000000000008028 RCX: ffffc9000a282000 RDX: 0000000000040000 RSI: ffffffff820e28d0 RDI: 0000000000000003 RBP: ffff888072591c30 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff820e21c7 R11: 00000000ffff8000 R12: ffff88802603d054 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f8a3dd98700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f51c4218718 CR3: 000000007dc31000 CR4: 0000000000350ee0 --- 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.
