invalid opcode in vmf_insert_pfn_prot

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: dcd68326d29b Merge tag 'devicetree-for-5.16' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10c433bcb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a89cd86e20989871
dashboard link: https://syzkaller.appspot.com/bug?extid=6e46aac06bd1bf24c5e3
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [air...@linux.ie christia...@amd.com dan...@ffwll.ch dri-...@lists.freedesktop.org linaro...@lists.linaro.org linux-...@vger.kernel.org linux...@vger.kernel.org maarten....@linux.intel.com mri...@kernel.org sumit....@linaro.org tzimm...@suse.de]

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

invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 4038 Comm: syz-executor.3 Not tainted 5.15.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:vmf_insert_pfn_prot+0x415/0x430 mm/memory.c:2117
Code: 92 c6 31 ff e8 9c cb c6 ff 84 db 74 2b e8 c3 c8 c6 ff e9 71 fd ff ff e8 b9 c8 c6 ff 0f 0b e8 b2 c8 c6 ff 0f 0b e8 ab c8 c6 ff <0f> 0b e8 64 9c 41 08 e8 9f c8 c6 ff 0f 0b e8 98 c8 c6 ff 0f 0b 66
RSP: 0000:ffffc9000309fa60 EFLAGS: 00010293
RAX: ffffffff81bd7c35 RBX: 0000000000000420 RCX: ffff888017dc0000
RDX: 0000000000000000 RSI: 0000000000000420 RDI: 0000000000000420
RBP: ffffc9000309fb20 R08: ffffffff81bd7920 R09: ffffffff81bd78f4
R10: 0000000000000002 R11: ffff888017dc0000 R12: 0000000008140476
R13: ffff88807263a840 R14: ffffc9000309faa0 R15: 0000000000019dfd
FS: 0000555555d51400(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200001c4 CR3: 000000003dcdb000 CR4: 00000000003526f0
DR0: 0000000000000005 DR1: 00000000000000ff DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
drm_gem_shmem_fault+0x1db/0x240 drivers/gpu/drm/drm_gem_shmem_helper.c:564
__do_fault+0x130/0x420 mm/memory.c:3859
do_cow_fault+0x27e/0xb50 mm/memory.c:4213
do_fault mm/memory.c:4314 [inline]
handle_pte_fault mm/memory.c:4570 [inline]
__handle_mm_fault mm/memory.c:4705 [inline]
handle_mm_fault+0x1bc4/0x2560 mm/memory.c:4803
do_user_addr_fault+0x8cc/0x10c0 arch/x86/mm/fault.c:1397
handle_page_fault arch/x86/mm/fault.c:1485 [inline]
exc_page_fault+0xa1/0x1e0 arch/x86/mm/fault.c:1541
asm_exc_page_fault+0x1e/0x30
RIP: 0033:0x7f73e14cef3a
Code: 30 48 8b 34 24 48 85 f6 74 17 8b 44 24 18 0f c8 89 c0 48 89 44 24 18 48 83 fe 01 0f 85 a1 01 00 00 48 8b 44 24 10 8b 74 24 18 <89> 30 e9 d2 fc ff ff 48 8b 44 24 10 8b 10 48 8b 04 24 48 85 c0 0f
RSP: 002b:00007ffee622c960 EFLAGS: 00010246
RAX: 00000000200001c4 RBX: 00007f73e1a45000 RCX: 0000000000000000
RDX: a840cab131e13144 RSI: 0000000000000000 RDI: 0000555555d512f0
RBP: 00007ffee622ca58 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000004 R11: 000000000005a53e R12: 00000000001cb4d5
R13: 00000000000003e8 R14: 00007f73e1640f60 R15: 00000000001cb443
</TASK>
Modules linked in:
---[ end trace 6dfdb368525c6e61 ]---
RIP: 0010:vmf_insert_pfn_prot+0x415/0x430 mm/memory.c:2117
Code: 92 c6 31 ff e8 9c cb c6 ff 84 db 74 2b e8 c3 c8 c6 ff e9 71 fd ff ff e8 b9 c8 c6 ff 0f 0b e8 b2 c8 c6 ff 0f 0b e8 ab c8 c6 ff <0f> 0b e8 64 9c 41 08 e8 9f c8 c6 ff 0f 0b e8 98 c8 c6 ff 0f 0b 66
RSP: 0000:ffffc9000309fa60 EFLAGS: 00010293
RAX: ffffffff81bd7c35 RBX: 0000000000000420 RCX: ffff888017dc0000
RDX: 0000000000000000 RSI: 0000000000000420 RDI: 0000000000000420
RBP: ffffc9000309fb20 R08: ffffffff81bd7920 R09: ffffffff81bd78f4
R10: 0000000000000002 R11: ffff888017dc0000 R12: 0000000008140476
R13: ffff88807263a840 R14: ffffc9000309faa0 R15: 0000000000019dfd
FS: 0000555555d51400(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200001c4 CR3: 000000003dcdb000 CR4: 00000000003526f0
DR0: 0000000000000005 DR1: 00000000000000ff DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 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.

[Dmitry Vyukov]

On Sun, 7 Nov 2021 at 12:33, syzbot
<syzbot+6e46aa...@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: dcd68326d29b Merge tag 'devicetree-for-5.16' of git://git...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=10c433bcb00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a89cd86e20989871
> dashboard link: https://syzkaller.appspot.com/bug?extid=6e46aac06bd1bf24c5e3
> compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
> CC: [air...@linux.ie christia...@amd.com dan...@ffwll.ch dri-...@lists.freedesktop.org linaro...@lists.linaro.org linux-...@vger.kernel.org linux...@vger.kernel.org maarten....@linux.intel.com mri...@kernel.org sumit....@linaro.org tzimm...@suse.de]
>
> 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+6e46aa...@syzkaller.appspotmail.com

It seems there was some bug in kernel BUG handling:

#syz dup: kernel BUG in vmf_insert_pfn_prot

> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/00000000000047b04305d0313e76%40google.com.