From: syzbot <syzbot+7d6f6855aee30f8bb7a5@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] upstream test error: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe
Date: Wed, 08 Dec 2021 09:23:21 -0800 [thread overview]
Message-ID: <0000000000001dba0805d2a5bf87@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 79a72162048e Merge tag 'xfs-5.16-fixes-2' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=167ed58db00000
kernel config: https://syzkaller.appspot.com/x/.config?x=5c733c28c0192584
dashboard link: https://syzkaller.appspot.com/bug?extid=7d6f6855aee30f8bb7a5
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+7d6f6855aee30f8bb7a5@syzkaller.appspotmail.com
executing program
executing program
executing program
executing program
executing program
2021/12/05 06:23:57 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@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2021-12-08 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 17:23 syzbot [this message]
2022-11-15 7:35 ` [syzbot] upstream test error: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000001dba0805d2a5bf87@google.com \
--to=syzbot+7d6f6855aee30f8bb7a5@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).