SYZFAIL: pthread_create failed

8 views
Skip to first unread message

syzbot

unread,
Apr 3, 2021, 12:37:19 PM4/3/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: bd634aa6 Linux 4.14.228
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12e02726d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=5fab202d11a349c3
dashboard link: https://syzkaller.appspot.com/bug?extid=b133c5c7555e280acf32

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

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

ioctl$SNDRV_TIMER_IOCTL_SELECT(0xffffffffffffffff, 0x40345410, &(0x7f0000000140)={{0xffffffffffffffff, 0x0, 0xffffffff, 0x1}})
clock_gettime(0x0, 0x0)
fork()
2021/04/03 16:36:15 executor 5 failed 11 times:
executor 5: exit status 67
SYZFAIL: pthread_create failed
(errno 11: Resource temporarily unavailable)
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

unread,
Apr 27, 2021, 4:30:21 AM4/27/21
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: cf256fbc Linux 4.14.231
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10dfa23ed00000
kernel config: https://syzkaller.appspot.com/x/.config?x=403e68efdb1dcca6
dashboard link: https://syzkaller.appspot.com/bug?extid=b133c5c7555e280acf32
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14d40799d00000

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

2021/04/27 07:24:29 executor failed 11 times: executor 1: failed to write control pipe: write |1: broken pipe
Reply all
Reply to author
Forward
0 new messages