Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37;
Message-ID: <f8891c2f-38f9-f741-66ad-8c5fbe1e365f@ghiti.fr>
Date:   Fri, 29 Sep 2023 12:56:30 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.15.1
Subject: Re: [syzbot] riscv/fixes test error: BUG: got no coverage: (3)
To:     syzbot <syzbot+2ecff9714d050e3c3a88@syzkaller.appspotmail.com>,
        aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org,
        linux-riscv@lists.infradead.org, palmer@dabbelt.com,
        paul.walmsley@sifive.com, syzkaller-bugs@googlegroups.com
References: <000000000000a8df0406061b76e6@google.com>
Content-Language: en-US
From:   Alexandre Ghiti <alex@ghiti.fr>
In-Reply-To: <000000000000a8df0406061b76e6@google.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 24/09/2023 16:14, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:    b06fab003ae1 riscv: kselftests: Fix mm build by removing t..
> git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
> console output: https://syzkaller.appspot.com/x/log.txt?x=16388918680000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=89f0a88d4bc7f0f4
> dashboard link: https://syzkaller.appspot.com/bug?extid=2ecff9714d050e3c3a88
> compiler:       riscv64-linux-gnu-gcc (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: riscv64
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/a741b348759c/non_bootable_disk-b06fab00.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/d751d3ead63f/vmlinux-b06fab00.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/d72380bd99cc/Image-b06fab00.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+2ecff9714d050e3c3a88@syzkaller.appspotmail.com
>
> executing program
> executing program
> executing program
> executing program
> 1970/01/01 00:05:53 SYZFATAL: BUG: got no coverage:


Not sure how to debug that, any idea what's wrong here?


> loop exited with status 11
>
>
> ---
> 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.
>
> If the bug is already fixed, let syzbot know by replying with:
> #syz fix: exact-commit-title
>
> If you want to overwrite bug's subsystems, reply with:
> #syz set subsystems: new-subsystem
> (See the list of subsystem names on the web dashboard)
>
> If the bug is a duplicate of another bug, reply with:
> #syz dup: exact-subject-of-another-report
>
> If you want to undo deduplication, reply with:
> #syz undup
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv