Hello, syzbot found the following issue on: HEAD commit: f02ac5c95dfd Add linux-next specific files for 20220427 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=134114c8f00000 kernel config: https://syzkaller.appspot.com/x/.config?x=e9256c70f586da8a dashboard link: https://syzkaller.appspot.com/bug?extid=7728e4ab5371cebc9c00 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+7728e4ab5371cebc9c00@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 0 PID: 16395 at mm/mmap.c:1072 vma_merge+0x428/0x950 mm/mmap.c:1072 Modules linked in: CPU: 0 PID: 16395 Comm: syz-executor.0 Not tainted 5.18.0-rc4-next-20220427-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:vma_merge+0x428/0x950 mm/mmap.c:1072 Code: 00 e8 5c 1f c4 ff e8 57 1f c4 ff 45 31 f6 e8 4f 1f c4 ff 4c 89 f0 48 83 c4 28 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 38 1f c4 ff <0f> 0b e9 6c fd ff ff e8 2c 1f c4 ff 48 8d bd 88 00 00 00 48 b8 00 RSP: 0018:ffffc90002dffc90 EFLAGS: 00010293 RSP: 0018:ffffc90002dffc90 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000008100077 RCX: 0000000000000000 RDX: ffff888076f91d40 RSI: ffffffff81b62968 RDI: 0000000000000003 RBP: ffff88801bea8000 R08: 0000000020600000 R09: 0000000000000000 R10: ffffffff81b626ce R11: 0000000000000000 R12: 0000000020ce2000 R13: 0000000020600000 R14: ffff8880791ba360 R15: ffff8880791ba360 FS: 0000555556995400(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020002a80 CR3: 000000003bbf8000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> userfaultfd_release+0x4c5/0x670 fs/userfaultfd.c:888 __fput+0x277/0x9d0 fs/file_table.c:317 task_work_run+0xdd/0x1a0 kernel/task_work.c:169 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] exit_to_user_mode_loop kernel/entry/common.c:169 [inline] exit_to_user_mode_prepare+0x23c/0x250 kernel/entry/common.c:201 __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline] syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:294 do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f394ce3bd2b Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 63 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 a1 fc ff ff 8b 44 RSP: 002b:00007ffc0fe56030 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00007f394ce3bd2b RDX: 00007f394cfa04b0 RSI: ffffffffffffffff RDI: 0000000000000004 RBP: 00007f394cf9d960 R08: 0000000000000000 R09: 00007f394cfa04b8 R10: 00007ffc0fe56130 R11: 0000000000000293 R12: 0000000000085752 R13: 00007ffc0fe56130 R14: 00007f394cf9bf60 R15: 0000000000000032 </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.
