witness: shared lock of (rwlock) maddr while exclusively lo
syzbot
syzbot found the following issue on:
HEAD commit: f9943f26ca81 Use an iterator in uvmpd_scan_active() to pre..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=170b2688580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=6b7178e744e6078d044d
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d6622753111d/disk-f9943f26.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/66335b49a51a/bsd-f9943f26.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a84aac66fddb/kernel-f9943f26.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6b7178...@syzkaller.appspotmail.com
login: witness: shared lock of (rwlock) maddr while exclusively lo
---
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