Hello,
syzbot found the following issue on:
HEAD commit: 2eb29d59ddf0 Merge tag 'drm-next-2023-03-03-1' of git://an..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=14b202bcc80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=cab35c936731a347
dashboard link:
https://syzkaller.appspot.com/bug?extid=ed68007dabd23f208d70
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [
ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/ea23ee201337/disk-2eb29d59.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/40a9db02dede/vmlinux-2eb29d59.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/8d4b574642d0/bzImage-2eb29d59.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+ed6800...@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xdffffc00000000fa: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x00000000000007d0-0x00000000000007d7]
CPU: 0 PID: 24576 Comm: syz-executor.1 Not tainted 6.2.0-syzkaller-13277-g2eb29d59ddf0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023
RIP: 0010:mm_has_notifiers include/linux/mmu_notifier.h:282 [inline]
RIP: 0010:mmu_notifier_invalidate_range_start include/linux/mmu_notifier.h:456 [inline]
RIP: 0010:unmap_vmas+0x1c9/0x380 mm/memory.c:1690
Code: 8c 41 b8 01 00 00 00 e8 25 14 a4 ff 4c 8b 6c 24 70 58 48 b8 00 00 00 00 00 fc ff df 49 8d bd d0 07 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 85 01 00 00 49 83 bd d0 07 00 00 00 0f 85 3b 01
RSP: 0018:ffffc90015e87ac8 EFLAGS: 00010216
RAX: dffffc0000000000 RBX: ffffffffffffffff RCX: ffffffff8165fc5c
RDX: 00000000000000fa RSI: 0000000000000000 RDI: 00000000000007d0
RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff914deb97
R10: fffffbfff229bd72 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: dffffc0000000000 R15: ffff88808765b7e0
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007faa78c27ec0 CR3: 0000000079aa1000 CR4: 0000000000350ef0
Call Trace:
<TASK>
exit_mmap+0x190/0x7d0 mm/mmap.c:3036
__mmput+0x128/0x4c0 kernel/fork.c:1209
mmput+0x60/0x70 kernel/fork.c:1231
exit_mm kernel/exit.c:563 [inline]
do_exit+0x9d7/0x2a40 kernel/exit.c:856
do_group_exit+0xd4/0x2a0 kernel/exit.c:1019
__do_sys_exit_group kernel/exit.c:1030 [inline]
__se_sys_exit_group kernel/exit.c:1028 [inline]
__x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1028
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7faa78c8c0f9
Code: Unable to access opcode bytes at 0x7faa78c8c0cf.
RSP: 002b:00007ffd893dc638 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007faa78c8c0f9
RDX: 00007faa78c89e2b RSI: 0000000000000000 RDI: 000000000000000b
RBP: 000000000000000b R08: 0000555556c93400 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000001 R15: 00007ffd893dcd00
</TASK>
Modules linked in:
----------------
Code disassembly (best guess):
0: 8c 41 b8 mov %es,-0x48(%rcx)
3: 01 00 add %eax,(%rax)
5: 00 00 add %al,(%rax)
7: e8 25 14 a4 ff callq 0xffa41431
c: 4c 8b 6c 24 70 mov 0x70(%rsp),%r13
11: 58 pop %rax
12: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
19: fc ff df
1c: 49 8d bd d0 07 00 00 lea 0x7d0(%r13),%rdi
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 85 01 00 00 jne 0x1b9
34: 49 83 bd d0 07 00 00 cmpq $0x0,0x7d0(%r13)
3b: 00
3c: 0f .byte 0xf
3d: 85 3b test %edi,(%rbx)
3f: 01 .byte 0x1
---
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.