syzbot


BUG: Bad page map

Status: closed as invalid on 2018/07/08 13:28
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 1551d, last: 1551d
similar bugs (9):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 BUG: Bad page map (3) 1 80d 80d 0/1 upstream: reported on 2022/07/18 21:41
upstream BUG: Bad page map (5) C 25 6h26m 158d 1/24 upstream: reported C repro on 2022/05/01 09:02
linux-4.19 BUG: Bad page map (2) 10 266d 447d 0/1 auto-closed as invalid on 2022/05/13 11:22
upstream BUG: Bad page map (2) syz 127 1492d 1548d 0/24 closed as invalid on 2018/09/05 12:51
upstream BUG: Bad page map (3) 4 1362d 1487d 0/24 auto-closed as invalid on 2019/07/13 00:02
linux-4.19 BUG: Bad page map 2 763d 822d 0/1 auto-closed as invalid on 2021/01/01 08:20
upstream BUG: Bad page map (4) 39 308d 944d 0/24 auto-closed as invalid on 2022/04/02 04:25
linux-4.14 BUG: Bad page map 1 809d 809d 0/1 auto-closed as invalid on 2020/11/16 16:05
android-54 BUG: Bad page map 1 43d 43d 0/2 upstream: reported on 2022/08/25 04:05

Sample crash report:
swap_info_get: Bad swap file entry 2003fffe20073304
BUG: Bad page map in process udevd  pte:ffff8801ccc12080 pmd:19a45d067
addr:00000000560bdde0 vm_flags:00000070 anon_vma:          (null) mapping:00000000e7420203 index:1c2
file:libnss_files-2.13.so fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
CPU: 0 PID: 12550 Comm: udevd Not tainted 4.18.0-rc3+ #48
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
PANIC: double fault, error_code: 0x0
Call Trace:
CPU: 1 PID: 12549 Comm: syz-executor2 Not tainted 4.18.0-rc3+ #48
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__lock_acquire+0x2e/0x5020 kernel/locking/lockdep.c:3294
Code: 41 
57 41 
89 cf 
41 56 
41 55 
49 89 
 print_bad_pte.cold.116+0x1cd/0x22b mm/memory.c:774
fd 41 
54 45 
89 cc 
53 65 
 zap_pte_range mm/memory.c:1380 [inline]
 zap_pmd_range mm/memory.c:1437 [inline]
 zap_pud_range mm/memory.c:1466 [inline]
 zap_p4d_range mm/memory.c:1487 [inline]
 unmap_page_range+0x1cb9/0x2220 mm/memory.c:1508
4c 8b 
34 25 
40 ee 
01 00 
48 83 
e4 f0 
48 81 
ec 60 
03 00 00 
48 8b 
45 10 
<89> 94 
24 80 
00 00 
00 48 
ba 00 
00 00 
00 00 
fc ff 
df 48 
 unmap_single_vma+0x1a0/0x310 mm/memory.c:1553
89 84 
 unmap_vmas+0x120/0x1f0 mm/memory.c:1583
24 98 
 exit_mmap+0x2c2/0x5b0 mm/mmap.c:3105
RSP: 0018:ffff880195a1bed0 EFLAGS: 00010082
 __mmput kernel/fork.c:970 [inline]
 mmput+0x265/0x620 kernel/fork.c:991
RAX: 0000000000000000 RBX: 1ffff10032b43856 RCX: 0000000000000002
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff88f92620
RBP: ffff880195a1c258 R08: 0000000000000000 R09: 0000000000000000
R10: ffff88019a9271b8 R11: ffff8801daf236b3 R12: 0000000000000000
R13: ffffffff88f92620 R14: ffff8801b3b0c240 R15: 0000000000000002
FS:  00007f0cc9e05700(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff880195a1bec8 CR3: 00000001bfd6a000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 exec_mmap fs/exec.c:1044 [inline]
 flush_old_exec+0xbaf/0x2100 fs/exec.c:1276

Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-bpf-next-kasan-gce 2018/07/08 12:12 bpf-next d90c936fb318 c9a7a4dc .config log report
* Struck through repros no longer work on HEAD.