From: syzbot ci <syzbot+ci156aec4dff349a40@syzkaller.appspotmail.com>
To: ajay.kaher@broadcom.com, akataria@vmware.com,
alexey.makhalov@broadcom.com, bp@alien8.de,
dave.hansen@linux.intel.com, dwmw2@infradead.org,
graf@amazon.de, hpa@zytor.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
pbonzini@redhat.com, seanjc@google.com, tglx@linutronix.de,
vkuznets@redhat.com, x86@kernel.org
Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot ci] Re: Support "generic" CPUID timing leaf as KVM guest and host.
Date: Fri, 15 Aug 2025 08:24:25 -0700 [thread overview]
Message-ID: <689f5129.050a0220.e29e5.0019.GAE@google.com> (raw)
In-Reply-To: <20250814120237.2469583-1-dwmw2@infradead.org>
syzbot ci has tested the following series
[v1] Support "generic" CPUID timing leaf as KVM guest and host.
https://lore.kernel.org/all/20250814120237.2469583-1-dwmw2@infradead.org
* [PATCH 1/3] KVM: x86: Restore caching of KVM CPUID base
* [PATCH 2/3] KVM: x86: Provide TSC frequency in "generic" timing infomation CPUID leaf
* [PATCH 3/3] x86/kvm: Obtain TSC frequency from CPUID if present
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/a9510b1a-8024-41ce-9775-675f5c165e20
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: dfc0f6373094dd88e1eaf76c44f2ff01b65db851
arch: amd64
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
config: https://ci.syzbot.org/builds/590edf8b-b2a0-4cbd-a80e-35083fe0988e/config
arch/x86/kernel/kvm.c:899:30: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes]
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
next prev parent reply other threads:[~2025-08-15 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 11:56 [PATCH 0/3] Support "generic" CPUID timing leaf as KVM guest and host David Woodhouse
2025-08-14 11:56 ` [PATCH 1/3] KVM: x86: Restore caching of KVM CPUID base David Woodhouse
2025-08-14 11:56 ` [PATCH 2/3] KVM: x86: Provide TSC frequency in "generic" timing infomation CPUID leaf David Woodhouse
2025-08-14 11:56 ` [PATCH 3/3] x86/kvm: Obtain TSC frequency from CPUID if present David Woodhouse
2025-08-15 15:24 ` syzbot ci [this message]
2025-08-15 15:36 ` [syzbot ci] Re: Support "generic" CPUID timing leaf as KVM guest and host David Woodhouse
2025-08-15 15:38 ` syzbot ci
2025-08-15 15:43 ` Aleksandr Nogikh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=689f5129.050a0220.e29e5.0019.GAE@google.com \
--to=syzbot+ci156aec4dff349a40@syzkaller.appspotmail.com \
--cc=ajay.kaher@broadcom.com \
--cc=akataria@vmware.com \
--cc=alexey.makhalov@broadcom.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=graf@amazon.de \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.