corrupted report (2)
2 views
Skip to first unread message
syzbot
May 28, 2020, 11:20:16 AM5/28/20
to syzkaller-f...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 4b8e3ae8 Fix NOINET6 build broken by r361575.
git tree: freebsd
console output: https://syzkaller.appspot.com/x/log.txt?x=178e11d6100000
dashboard link: https://syzkaller.appspot.com/bug?extid=8850eba0ff62f60a29ff
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+8850eb...@syzkaller.appspotmail.com
Waiting for PIDS: 424panic: Bad tailq NEXT(0xfffff80003b66b50->tqh_last) != NULL
cpuid = 0
time = 1590679151
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame 0xfffffe0027a54140
vpanic() at vpanic+0x1c7/frame 0xfffffe0027a541a0
panic() at panic+0x43/frame 0xfffffe0027a54200
pf_tagname2tag() at pf_tagname2tag+0x2c5/frame 0xfffffe0027a54260
pfioctl() at pfioctl+0x7385/frame 0xfffffe0027a54790
devfs_ioctl() at devfs_ioctl+0x14e/frame 0xfffffe0027a547f0
VOP_IOCTL_APV() at VOP_IOCTL_APV+0x78/frame 0xfffffe0027a54820
vn_ioctl() at vn_ioctl+0x27c/frame 0xfffffe0027a54940
devfs_ioctl_f() at devfs_ioctl_f+0x47/frame 0xfffffe0027a54980
kern_ioctl() at kern_ioctl+0x3d4/frame 0xfffffe0027a549f0
sys_ioctl() at sys_ioctl+0x22b/frame 0xfffffe0027a54ac0
amd64_syscall() at amd64_syscall+0x262/frame 0xfffffe0027a54bf0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe0027a54bf0
--- syscall (198, FreeBSD ELF64, nosys), rip = 0x28289a, rsp = 0x7fffdff9af08, rbp = 0x7fffdff9af70 ---
KDB: enter: panic
[ thread pid 1479 tid 100925 ]
Stopped at kdb_enter+0x67: movq $0,0x14a7706(%rip)
db>
db> serialport: VM disconnected.
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following crash on:
HEAD commit: 4b8e3ae8 Fix NOINET6 build broken by r361575.
git tree: freebsd
console output: https://syzkaller.appspot.com/x/log.txt?x=178e11d6100000
dashboard link: https://syzkaller.appspot.com/bug?extid=8850eba0ff62f60a29ff
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+8850eb...@syzkaller.appspotmail.com
Waiting for PIDS: 424panic: Bad tailq NEXT(0xfffff80003b66b50->tqh_last) != NULL
cpuid = 0
time = 1590679151
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame 0xfffffe0027a54140
vpanic() at vpanic+0x1c7/frame 0xfffffe0027a541a0
panic() at panic+0x43/frame 0xfffffe0027a54200
pf_tagname2tag() at pf_tagname2tag+0x2c5/frame 0xfffffe0027a54260
pfioctl() at pfioctl+0x7385/frame 0xfffffe0027a54790
devfs_ioctl() at devfs_ioctl+0x14e/frame 0xfffffe0027a547f0
VOP_IOCTL_APV() at VOP_IOCTL_APV+0x78/frame 0xfffffe0027a54820
vn_ioctl() at vn_ioctl+0x27c/frame 0xfffffe0027a54940
devfs_ioctl_f() at devfs_ioctl_f+0x47/frame 0xfffffe0027a54980
kern_ioctl() at kern_ioctl+0x3d4/frame 0xfffffe0027a549f0
sys_ioctl() at sys_ioctl+0x22b/frame 0xfffffe0027a54ac0
amd64_syscall() at amd64_syscall+0x262/frame 0xfffffe0027a54bf0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe0027a54bf0
--- syscall (198, FreeBSD ELF64, nosys), rip = 0x28289a, rsp = 0x7fffdff9af08, rbp = 0x7fffdff9af70 ---
KDB: enter: panic
[ thread pid 1479 tid 100925 ]
Stopped at kdb_enter+0x67: movq $0,0x14a7706(%rip)
db>
db> serialport: VM disconnected.
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot
Sep 27, 2020, 1:23:14 PM9/27/20
to syzkaller-f...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages