syzbot


assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c

Status: upstream: reported on 2024/04/17 21:34
Reported-by: syzbot+90b9aac60da3a5360280@syzkaller.appspotmail.com
First crash: 60d, last: 19d

Sample crash report:
panic: kernel diagnostic assertion "(pg->pg_flags & PG_BUSY) == 0" failed: file "/syzkaller/managers/main/kernel/sys/arch/amd64/amd64/pmap.c", line 1422
Starting stack trace...
panic(ffffffff82934da0) at panic+0x159 sys/kern/subr_prf.c:229
__assert(ffffffff828e8ca5,ffffffff8284054a,58e,ffffffff82896bc1) at __assert+0x29 sys/kern/subr_prf.c:157
pmap_destroy(fffffd8074ed87a0) at pmap_destroy+0x2a4 sys/arch/amd64/amd64/pmap.c:1422
uvm_map_teardown(fffffd806926c418) at uvm_map_teardown+0x287 sys/uvm/uvm_map.c:2557
uvmspace_free(fffffd806926c418) at uvmspace_free+0x96 sys/uvm/uvm_map.c:3461
vm_teardown(ffff800037815900) at vm_teardown+0x105 sys/dev/vmm/vmm.c:555
vm_terminate(ffff800037815ba0) at vm_terminate+0x121 sys/dev/vmm/vmm.c:688
vmmioctl(a00,80045604,ffff800037815ba0,1,ffff80002f508038) at vmmioctl+0x291 sys/dev/vmm/vmm.c:248
VOP_IOCTL(fffffd806ed310d8,80045604,ffff800037815ba0,1,fffffd807f7d78f0,ffff80002f508038) at VOP_IOCTL+0x91 sys/kern/vfs_vops.c:264
vn_ioctl(fffffd806a6e32d8,80045604,ffff800037815ba0,ffff80002f508038) at vn_ioctl+0xbb sys/kern/vfs_vnops.c:525
sys_ioctl(ffff80002f508038,ffff800037815d80,ffff800037815cd0) at sys_ioctl+0x4a5
syscall(ffff800037815d80) at syscall+0x72a sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x5204e400840, count: 244
End of stack trace.
syncing disks...26 18 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1  giving up

dump to dev 4,1 not possible
rebooting...
SeaBIOS (version 1.8.2-google)
Total RAM Size = 0x0000000080000000 = 2048 MiB
CPUs found: 2     Max CPUs supported: 2
SeaBIOS (version 1.8.2-google)
Machine UUID 1f64d870-06f2-d8bf-7327-adc6877a2997
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=4194304 = 2048 MiB
drive 0x000f27c0: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Sending Seabios boot VM event.
Booting from Hard Disk 0...
>> OpenBSD/amd64 BOOT 3.65
boot> machine ddbcpu 0
machine: syntax error
boot> trace
|/-\|/-\|/booting hd0a:trace: -\|/open hd0a:trace: No such file or directory
 failed(2). will try /bsd
boot> machine ddbcpu 1
machine: syntax error
boot> trace

Crashes (28):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/05/29 04:56 openbsd f475ad27b09c 34889ee3 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/28 12:53 openbsd 2ee83f25fcae 34889ee3 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/28 00:54 openbsd 98f39564523a f550015e .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/27 16:38 openbsd bc2c23e056db 761766e6 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/25 10:08 openbsd 92850d3aeacc a10a183e .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/24 14:29 openbsd 6859a790d2a4 8f98448e .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/22 10:25 openbsd 6859a790d2a4 4d098039 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/19 11:04 openbsd 63371a7f711d c0f1611a .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/19 02:51 openbsd 088a2cd995ac c0f1611a .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/17 15:21 openbsd 77ba8c170614 c2e07261 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/17 10:39 openbsd 77ba8c170614 c2e07261 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/16 14:02 openbsd b20edd337af0 ef5d53ed .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/15 06:17 openbsd b613adb4fae8 fdb4c10c .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/13 22:31 openbsd aa47c49a2e9a fdb4c10c .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/12 12:45 openbsd 73556a19205d 9026e142 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/12 02:53 openbsd 73556a19205d 9026e142 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/12 01:58 openbsd 73556a19205d 9026e142 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/07 07:52 openbsd 21e142091427 fa7a5cf0 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/06 17:54 openbsd 27da0d9a6e0d d884b519 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/06 04:36 openbsd 4580bd6ebd98 610f2a54 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/06 02:42 openbsd 4580bd6ebd98 610f2a54 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/05 21:31 openbsd 5ec8126aae72 610f2a54 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/05 18:51 openbsd 5ec8126aae72 610f2a54 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/05/02 05:23 openbsd 82673a188a32 3ba885bc .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/04/28 22:03 openbsd b98581f594cd 07b455f9 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/04/27 19:19 openbsd 22bab8566a4f 07b455f9 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/04/18 11:22 openbsd 3a96f17f8ee6 bd38b692 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
2024/04/17 21:33 openbsd 456e8b6ad58e acc528cb .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main assert "(pg->pg_flags & PG_BUSY) == NUM" failed in pmap.c
* Struck through repros no longer work on HEAD.