netdev - [syzbot] net test error: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe

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 for Android: free password hash cracker in your pocket

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

Message-ID: <000000000000a9cf6105d4c2f0ee@google.com>
Date:   Tue, 04 Jan 2022 07:03:29 -0800
From:   syzbot <syzbot+acdc85fe587a899a4336@...kaller.appspotmail.com>
To:     davem@...emloft.net, kuba@...nel.org, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] net test error: BUG: program execution failed: executor NUM:
 failed to write control pipe: write |NUM: broken pipe

Hello,

syzbot found the following issue on:

HEAD commit:    4760abaac684 Merge branch 'mpr-len-checks' David Ahern says:
git tree:       net
console output: https://syzkaller.appspot.com/x/log.txt?x=10b49a35b00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1a86c22260afac2f
dashboard link: https://syzkaller.appspot.com/bug?extid=acdc85fe587a899a4336
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+acdc85fe587a899a4336@...kaller.appspotmail.com

2021/12/31 14:59:00 checking revisions...
2021/12/31 14:59:01 testing simple program...
executing program
executing program
executing program
2021/12/31 14:59:12 BUG: program execution failed: executor 0: failed to write control pipe: write |1: broken pipe
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.