SYZFAIL: clock_gettime failed

8 views
Skip to first unread message

syzbot

unread,
Dec 11, 2021, 7:59:25 PM12/11/21
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 4fd09f7a7972 UPSTREAM: HID: wacom: fix problems when devic..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=145c8a69b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8844969a6709ae53
dashboard link: https://syzkaller.appspot.com/bug?extid=a15b5d5a14991da8eb6c
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12216741b00000

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

2021/12/12 00:55:29 executor failed 11 times: executor 0: exit status 67
SYZFAIL: clock_gettime failed
(errno 14: Bad address)
SYZFAIL: child failed
(errno 0: Success)
loop exited with status 67

SYZFAIL: clock_gettime failed
(errno 14: Bad address)
SYZFAIL: child failed
(errno 0: Success)
loop exited with status 67


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

syzbot

unread,
Oct 7, 2023, 12:00:57 PM10/7/23
to syzkaller-a...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages