Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:1 as permitted sender) client-ip=2620:137:e000::3:1;
MIME-Version: 1.0
Date:   Sun, 24 Sep 2023 07:14:44 -0700
Message-ID: <000000000000a8df0406061b76e6@google.com>
Subject: [syzbot] riscv/fixes test error: BUG: got no coverage: (3)
From:   syzbot <syzbot+2ecff9714d050e3c3a88@syzkaller.appspotmail.com>
To:     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
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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:
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