Messages in this thread | | | From | Dmitry Vyukov <> | Date | Tue, 15 Nov 2022 08:35:15 +0100 | Subject | Re: [syzbot] upstream test error: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe |
| |
On Wed, 8 Dec 2021 at 18:23, syzbot <syzbot+7d6f6855aee30f8bb7a5@syzkaller.appspotmail.com> wrote: > > 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
This was fixed in syzkaller.
#syz invalid
> 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.
| |