From: syzbot ci <syzbot+ci4cf204126508c574@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: x86/fred: Fix early boot failures on SEV-ES/SNP guests
Date: Wed, 04 Feb 2026 22:10:43 -0800 [thread overview]
Message-ID: <69843463.050a0220.3b3015.0019.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] x86/fred: Fix early boot failures on SEV-ES/SNP guests
https://lore.kernel.org/all/20260205051030.1225975-1-nikunj@amd.com
* [PATCH] x86/fred: Fix early boot failures on SEV-ES/SNP guests
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/4b020042-5efd-47f8-a065-ef24bf5af659
***
kernel build error
tree: linux-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base: 0f8a890c4524d6e4013ff225e70de2aed7e6d726
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/af53275e-610d-499c-8272-fb848e13a00c/config
arch/x86/entry/entry_fred.c:213:11: error: call to undeclared function 'user_exc_vmm_communication'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
arch/x86/entry/entry_fred.c:213:4: error: void function 'fred_hwexc' should not return a value [-Wreturn-mismatch]
arch/x86/entry/entry_fred.c:215:11: error: call to undeclared function 'kernel_exc_vmm_communication'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
arch/x86/entry/entry_fred.c:215:4: error: void function 'fred_hwexc' should not return a value [-Wreturn-mismatch]
***
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.
The email will later be sent to:
[bp@alien8.de dave.hansen@linux.intel.com hpa@zytor.com jon.grimm@amd.com kvm@vger.kernel.org linux-kernel@vger.kernel.org mingo@redhat.com nikunj@amd.com pbonzini@redhat.com seanjc@google.com stable@vger.kernel.org tglx@kernel.org thomas.lendacky@amd.com x86@kernel.org xin@zytor.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-02-05 6:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=69843463.050a0220.3b3015.0019.GAE@google.com \
--to=syzbot+ci4cf204126508c574@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox