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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <0000000000000ee81005e71fbcd8@google.com>
Date:   Fri, 26 Aug 2022 00:19:28 -0700
From:   syzbot <syzbot+eb8c1c76ad86ed1cd820@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
        sfr@...b.auug.org.au, syzkaller-bugs@...glegroups.com
Subject: [syzbot] linux-next test error: BUG: program execution failed:
 executor NUM: exit status NUM (3)

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+eb8c1c76ad86ed1cd820@...kaller.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 syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.