Re: [moderation/CI] Re: Cleaning up the KVM clock mess

Aleksandr Nogikh <[email protected]> Thu, 30 Jul 2026 15:40:04 +0200
Newsgroups dev.linux.lists.syzbot
Message-ID <CANp29Y4TTLG-=O-Vd9D_7t04RbUOqhLQUbuCUgRFdphq-DBf7w@mail.gmail.com>
Thanks for triaging this report!

The CI did recognize the base commit, but it didn't know about the
kvm-x86 tree, so couldn't fetch it.
I've added it in
https://github.com/google/syzkaller/commit/285e8c809b7ce04c728f02b57698320b=
cc0efa48

--=20
Aleksandr

On Thu, Jul 30, 2026 at 10:36=E2=80=AFAM David Woodhouse <[email protected]=
rg> wrote:
>
> #syz invalid
>
> The series (or at least patch 01/36) was posted with
>
>   base-commit: 271255273d5ff348fe29d89fe4712b2f7f7907c3
>
> which is the tip of kvm-x86/next and contains the timekeeping
> prerequisites (ktime_get_snapshot_id() et al). The CI applied it to a
> kvm-next tree at a204badd8432 which predates them, hence the build
> failure. Wrong base tree, not a bug in the series.
>
> --
> You received this message because you are subscribed to the Google Groups=
 "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an=
 email to [email protected].
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller=
-upstream-moderation/b5e3e5c81ebcbf4f6a793b89463e4979fc7cba4d.camel%40infra=
dead.org.