Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33;
MIME-Version: 1.0
References: <000000000000a8df0406061b76e6@google.com> <f8891c2f-38f9-f741-66ad-8c5fbe1e365f@ghiti.fr>
In-Reply-To: <f8891c2f-38f9-f741-66ad-8c5fbe1e365f@ghiti.fr>
From:   Aleksandr Nogikh <nogikh@google.com>
Date:   Fri, 29 Sep 2023 13:40:41 +0200
Message-ID: <CANp29Y7wO0OrrDCauTK_O2Rf=vrqVwrUGmHy-hanSKvWexJpyQ@mail.gmail.com>
Subject: Re: [syzbot] riscv/fixes test error: BUG: got no coverage: (3)
To:     Alexandre Ghiti <alex@ghiti.fr>
Cc:     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
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Fri, Sep 29, 2023 at 12:56=E2=80=AFPM Alexandre Ghiti <alex@ghiti.fr> wr=
ote:
>
> On 24/09/2023 16:14, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:    b06fab003ae1 riscv: kselftests: Fix mm build by removin=
g t..
> > git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/riscv/lin=
ux.git fixes
> > console output: https://syzkaller.appspot.com/x/log.txt?x=3D16388918680=
000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=3D89f0a88d4bc=
7f0f4
> > dashboard link: https://syzkaller.appspot.com/bug?extid=3D2ecff9714d050=
e3c3a88
> > 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/vmli=
nux-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 co=
mmit:
> > 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?

The error message means that KCOV did not return any kernel coverage
to syzkaller when it should have returned at least something.

It was recorded on syzbot only once ~ a week ago and, since then,
syzbot has been able to build and boot newer kernel revisions. So the
report is no longer really worth investigating. Let's invalidate it.

#syz invalid

>
>
> > loop exited with status 11
> >
> >