linux-kernel - Re: [syzbot] upstream 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CACT4Y+Z-Mi-F8V_stvFvPdzyfnmcYwLp986gyQ=Z0amvsC4_fA@mail.gmail.com>
Date:   Tue, 15 Nov 2022 08:35:15 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     syzbot <syzbot+7d6f6855aee30f8bb7a5@...kaller.appspotmail.com>
Cc:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
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@...kaller.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@...kaller.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@...glegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.