Hello,
syzbot found the following issue on:
HEAD commit: 11531c4859ff static int, not int static
git tree: openbsd
console output:
https://syzkaller.appspot.com/x/log.txt?x=1629e77c580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link:
https://syzkaller.appspot.com/bug?extid=5662dac8492de78ac399
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/cd199ce87ac7/disk-11531c48.raw.xz
bsd.gdb:
https://storage.googleapis.com/syzbot-assets/77e328be24cf/bsd-11531c48.gdb.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/2c0bd2348d13/kernel-11531c48.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+5662da...@syzkaller.appspotmail.com
panic: kernel diaWgARnostNiIcN aGs:s SPeLr tNOioTn L"O(WpgER-E>D pONg SY_fSlCaAgLs L& 9 1 (P16Q6_3I30NACT501IV6E E|PXQIT_A 0C 3
TIStopped at savectx+0xae: movl $0,%gs:0x688
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*251608 37253 0 0x2 0 0 syz-executor
savectx() at savectx+0xae
end of kernel
end trace frame: 0x703f63240520, count: 14
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports. Insufficient info makes it difficult to find and fix bugs.
---
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