kernel BUG in validate_mm_rb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: eb575cd5 Linux 4.19.195
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=167f1bdc300000
kernel config: https://syzkaller.appspot.com/x/.config?x=5506475cccaff975
dashboard link: https://syzkaller.appspot.com/bug?extid=fa8ace605f2b9ea170c2

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+fa8ace...@syzkaller.appspotmail.com

next ffff888000102b98 prev ffff888000102da8 mm ffff88808f057600
prot 8000000000000025 anon_vma ffff88809c035040 vm_ops ffffffff887a2e80
pgoff 14 file ffff8880997c8280 private_data 0000000000000000
flags: 0x8100071(read|mayread|maywrite|mayexec|account|softdirty)
------------[ cut here ]------------
kernel BUG at mm/mmap.c:350!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 4947 Comm: systemd-udevd Not tainted 4.19.195-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:validate_mm_rb+0x97/0xb0 mm/mmap.c:350
Code: 7d 18 4c 89 e7 e8 f9 f2 ff ff 49 89 c5 48 89 c6 4c 89 ff e8 bb ed d4 ff 4d 39 ef 74 a7 e8 a1 ec d4 ff 4c 89 e7 e8 19 22 66 06 <0f> 0b 5b 5d 41 5c 41 5d 41 5e 41 5f e9 88 ec d4 ff e8 43 b9 0a 00
RSP: 0018:ffff88823af7fdc0 EFLAGS: 00010287
RAX: 0000000000000147 RBX: ffff8880a3005b98 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dfc91 RDI: ffffed10475eff93
RBP: ffff888000102ed0 R08: 0000000000000147 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888000102eb0
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000557b01b39000
FS: 00007f05a61108c0(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000557b01e47160 CR3: 000000023a8d6000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
vma_rb_erase mm/mmap.c:457 [inline]
detach_vmas_to_be_unmapped mm/mmap.c:2591 [inline]
do_munmap+0x4d1/0xde0 mm/mmap.c:2780
vm_munmap+0xda/0x140 mm/mmap.c:2800
__do_sys_munmap mm/mmap.c:2810 [inline]
__se_sys_munmap mm/mmap.c:2807 [inline]
__x64_sys_munmap+0x5d/0x80 mm/mmap.c:2807
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f05a4f8b6e7
Code: c7 c0 ff ff ff ff eb 8d 48 8b 15 ac 47 2b 00 f7 d8 64 89 02 e9 5b ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 b8 0b 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 81 47 2b 00 f7 d8 64 89 01 48
RSP: 002b:00007fffa06fbe88 EFLAGS: 00000206 ORIG_RAX: 000000000000000b
RAX: ffffffffffffffda RBX: 0000557b01e40100 RCX: 00007f05a4f8b6e7
RDX: 0000000000000080 RSI: 000000000080ccec RDI: 00007f05a3e19000
RBP: 0000557b01ba9d18 R08: 0000557b01e40c00 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000206 R12: 0000557b01e400e0
R13: 0000000000000000 R14: 0000000000000003 R15: 000000000000000e
Modules linked in:
---[ end trace b0f009cdb54242aa ]---
RIP: 0010:validate_mm_rb+0x97/0xb0 mm/mmap.c:350
Code: 7d 18 4c 89 e7 e8 f9 f2 ff ff 49 89 c5 48 89 c6 4c 89 ff e8 bb ed d4 ff 4d 39 ef 74 a7 e8 a1 ec d4 ff 4c 89 e7 e8 19 22 66 06 <0f> 0b 5b 5d 41 5c 41 5d 41 5e 41 5f e9 88 ec d4 ff e8 43 b9 0a 00
RSP: 0018:ffff88823af7fdc0 EFLAGS: 00010287
RAX: 0000000000000147 RBX: ffff8880a3005b98 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dfc91 RDI: ffffed10475eff93
RBP: ffff888000102ed0 R08: 0000000000000147 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888000102eb0
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000557b01b39000
FS: 00007f05a61108c0(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000557b01e47160 CR3: 000000023a8d6000 CR4: 00000000001406f0
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.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.