panic:p a nic : kernel diagnostic assertion "((flags & PGO_LOCKED) != NUM && rw_lock_held(uobj->vmobjlock)) || (flags &

1 view
Skip to first unread message

syzbot

unread,
May 20, 2024, 8:28:33 AMMay 20
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ab5fd4cb8341 drm/amdkfd: don't allow mapping the MMIO HDP ..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=15a2be58980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=38abe43a803a7d0f344a

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8058083224db/disk-ab5fd4cb.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/850ce86718c8/bsd-ab5fd4cb.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6c64c3ced325/kernel-ab5fd4cb.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+38abe4...@syzkaller.appspotmail.com

panic:p a nic : kernel diagnostic assertion "((flags & PGO_LOCKED) != 0 && rw_lock_held(uobj->vmobjlock)) || (flags & PGO_LOCKED) == 0" failed: file "/syzkaller/managers/multicore/kernel/sys/uvm/uvm_vnode.c", line 953
Starting stack trace...
panic(ffffffff8295dda1) at panic+0x16f sys/kern/subr_prf.c:229
__assert(ffffffff829111d8,ffffffff82850827,3b9,ffffffff8292ce3b) at __assert+0x29 sys/kern/subr_prf.c:157
uvn_get(fffffd806d7eff18,19000,ffff80002a2295c0,ffff80002a22943c,3,4,7aabd48b6abd0109,19000) at uvn_get+0x4ca sys/uvm/uvm_vnode.c:952
uvm_fault_lower_lookup(ffff80002a229640,ffff80002a229678,ffff80002a2295c0) at uvm_fault_lower_lookup+0xf3 sys/uvm/uvm_fault.c:1128
uvm_fault_lower(ffff80002a229640,ffff80002a229678,ffff80002a2295c0,0) at uvm_fault_lower+0x62 sys/uvm/uvm_fault.c:1227
uvm_fault(fffffd806944e8b0,ac752fc1000,0,4) at uvm_fault+0x255 sys/uvm/uvm_fault.c:637
upageflttrap(ffff80002a2297c0,ac752fc11a0) at upageflttrap+0x8e sys/arch/amd64/amd64/trap.c:188
usertrap(ffff80002a2297c0) at usertrap+0x22a sys/arch/amd64/amd64/trap.c:436
recall_trap() at recall_trap+0x8
end of kernel
end trace frame: 0xac9ea6a48a0, count: 248
End of stack trace.

dump to dev 4,1 not possible


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages