[syzbot] linux-next test error: BUG: program execution failed: executor NUM: exit status NUM (3)

12 views
Skip to first unread message

syzbot

unread,
Aug 26, 2022, 3:19:30 AM8/26/22
to linux-...@vger.kernel.org, linux...@vger.kernel.org, s...@canb.auug.org.au, syzkall...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: cc2986f4dc67 Add linux-next specific files for 20220822
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11573e2d080000
kernel config: https://syzkaller.appspot.com/x/.config?x=2aea846fde08e662
dashboard link: https://syzkaller.appspot.com/bug?extid=eb8c1c76ad86ed1cd820
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

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

2022/08/22 07:08:16 checking machine...
2022/08/22 07:08:16 checking revisions...
2022/08/22 07:08:17 testing simple program...
executing program
2022/08/22 07:08:20 SYZFATAL: BUG: program execution failed: executor 0: exit status 67
SYZFAIL: wrong response packet
(errno 16: Device or resource busy)
loop exited with status 67

SYZFAIL: wrong response packet
(errno 16: Device or resource busy)
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,
Nov 20, 2022, 4:57:31 AM11/20/22
to syzkall...@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