witness: lock_obwitness_checkordwitness_checkordrw_enter_write(ADDR)rw_enter_write+0unveil_delete_naunveil_delete_naunve

3 views
Skip to first unread message

syzbot

unread,
Oct 1, 2024, 2:12:27 PM10/1/24
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 67526adf6fb7 Adjust ptrace interface to properly suport si..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=17868927980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=52dc7e304c7580fb749e

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f8459e04f0c/disk-67526adf.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/eda12b8519de/bsd-67526adf.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6c602291a493/kernel-67526adf.xz

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

pmap_unwire: wiring for pmap 0xfffffd8065fe04e8 va 0xbd0f29b7pmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirpmap_unwire: wirwitness: lock_obwitness_checkordwitness_checkordrw_enter_write(ffff80000161d018)rw_enter_write+0unveil_delete_naunveil_delete_naunveil_destroy(ffff800036dac4a8)unveil_destroy+0exit1(ffff800037exit1+0x7d1
sys_exit(ffff800037201700,ffff80003sys_exit+0x1a
syscall(ffff80003721f1c0) at syscall+0xaf8 mi_syscall sys/sys/syscall_mi.h:179 [inline]
syscall(ffff80003721f1c0) at syscall+0xaf8 sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x72915trace
x86_ipi_db(ffff800029b7bff0) at x86_ipi_db+0x27 sys/arch/amd64/amd64/db_interface.c:393
x86_ipi_handler() at x86_ipi_handler+0xd9 sys/arch/amd64/amd64/ipi.c:106
Xresume_lapic_ipi() at Xresume_lapic_ipi+0x27
__mp_lock(ffffffff835af478) at __mp_lock+0x192 __mp_lock_spin sys/kern/kern_lock.c:113 [inline]
__mp_lock(ffffffff835af478) at __mp_lock+0x192 sys/kern/kern_lock.c:144
vn_ioctl(fffffd8071ec10b8,80044b02,ffff8000372cd650,ffff8000ffff3970) at vn_ioctl+0x4d sys/kern/vfs_vnops.c:508
sys_ioctl(ffff8000ffff3970,ffff8000372cd830,ffff8000372cd780) at sys_ioctl+0x67c
syscall(ffff8000372cd830) at syscall+0xbb6 mi_syscall sys/sys/syscall_mi.h:179 [inline]
syscall(ffff8000372cd830) at syscall+0xbb6 sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xf4302395470, count: -8


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

syzbot

unread,
Dec 30, 2024, 1:12:22 PM12/30/24
to syzkaller-o...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages