syzbot


kernel BUG at mm/memory.c:LINE!

Status: upstream: reported C repro on 2020/05/21 23:25
Reported-by: syzbot+c464fddc58432bbf3f44@syzkaller.appspotmail.com
First crash: 1459d, last: 558d
Fix bisection the fix commit could be any of (bisect log):
  a41ba30d9df2 Linux 4.14.181
  4139fb08c05f Linux 4.14.187
  
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 kernel BUG at mm/memory.c:LINE! C error 8 560d 1459d 0/1 upstream: reported C repro on 2020/05/21 22:29
upstream kernel BUG in __handle_mm_fault mm 2 1115d 1115d 0/26 auto-closed as invalid on 2021/06/29 08:42
upstream kernel BUG in vmf_insert_pfn_prot C done done 1933 371d 975d 22/26 fixed on 2023/06/14 22:21
upstream kernel BUG at mm/memory.c:LINE! fs mm 1 2142d 2141d 8/26 fixed on 2018/08/08 18:10

Sample crash report:
next ffff8880a8f5fca0 prev ffff8880a8f5fb98 mm ffff8880b56c9900
prot 8000000000000025 anon_vma           (null) vm_ops ffffffff8790b420
pgoff 0 file ffff8880b0488300 private_data           (null)
flags: 0xfa(write|shared|mayread|maywrite|mayexec|mayshare)
------------[ cut here ]------------
kernel BUG at mm/memory.c:4016!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 7974 Comm: syz-executor421 Not tainted 4.14.298-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
task: ffff8880b523c080 task.stack: ffff888096480000
RIP: 0010:wp_huge_pmd mm/memory.c:4016 [inline]
RIP: 0010:__handle_mm_fault+0x259a/0x4620 mm/memory.c:4224
RSP: 0000:ffff888096487d20 EFLAGS: 00010287
RAX: 0000000000000140 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff878bd060 RDI: ffffed1012c90f83
RBP: 1ffff11012c90faa R08: 0000000000000140 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 800000008ac000e5
R13: ffff888099f6ea90 R14: 00000000000000e5 R15: ffffffff88ccb358
FS:  0000555556c48300(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007feea4695000 CR3: 0000000099d30000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 handle_mm_fault+0x455/0x9c0 mm/memory.c:4271
 __do_page_fault+0x549/0xad0 arch/x86/mm/fault.c:1442
 page_fault+0x45/0x50 arch/x86/entry/entry_64.S:1126
Code: 1d ec f6 ff e9 de e9 ff ff e8 43 ab df ff 4c 89 ef e8 cb 40 02 00 45 31 f6 e9 88 f5 ff ff e8 2e ab df ff 4c 89 ef e8 fc 2c 8e 05 <0f> 0b e8 1f ab df ff 49 8d bc 24 88 00 00 00 48 b8 00 00 00 00 
RIP: wp_huge_pmd mm/memory.c:4016 [inline] RSP: ffff888096487d20
RIP: __handle_mm_fault+0x259a/0x4620 mm/memory.c:4224 RSP: ffff888096487d20
---[ end trace d0271fcce5c58a0d ]---

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/11/08 22:16 linux-4.14.y a901bb6c7db7 060f945e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 kernel BUG in __handle_mm_fault
2022/06/13 08:23 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 kernel BUG in __handle_mm_fault
2020/05/21 23:24 linux-4.14.y a41ba30d9df2 4afdfa20 .config console log report syz ci2-linux-4-14
2020/08/14 11:27 linux-4.14.y 14b58326976d 54ce1ed6 .config console log report ci2-linux-4-14
* Struck through repros no longer work on HEAD.