From: syzbot ci <syzbot+ci0d589002099e63f1@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: KVM: pfncache: Add guest_memfd support to pfncache
Date: Tue, 10 Mar 2026 06:38:29 -0700 [thread overview]
Message-ID: <69b01ed5.a70a0220.be77.0114.GAE@google.com> (raw)
syzbot ci has tested the following series
[v3] KVM: pfncache: Add guest_memfd support to pfncache
https://lore.kernel.org/all/20260310063647.15665-1-itazur@amazon.com
* [RFC PATCH v3 1/6] KVM: pfncache: Resolve PFNs via kvm_gmem_get_pfn() for gmem-backed GPAs
* [RFC PATCH v3 2/6] KVM: pfncache: Obtain KHVA via vmap() for gmem with NO_DIRECT_MAP
* [RFC PATCH v3 3/6] KVM: Rename invalidate_begin to invalidate_start for consistency
* [RFC PATCH v3 4/6] KVM: pfncache: Rename invalidate_start() helper
* [RFC PATCH v3 5/6] KVM: Rename mn_* invalidate-related fields to generic ones
* [RFC PATCH v3 6/6] KVM: pfncache: Invalidate on gmem invalidation and memattr updates
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/ccfe2969-11ff-4a60-b754-7e88e8a233a5
***
kernel build error
tree: kvm-next
URL: https://kernel.googlesource.com/pub/scm/virt/kvm/kvm/
base: e89f0e9a0a007e8c3afb8ecd739c0b3255422b00
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/1ac93cba-4964-499e-b638-ce065647b0dd/config
arch/x86/kvm/../../../virt/kvm/pfncache.c:107:18: error: call to undeclared function 'mapping_no_direct_map'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
***
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:
[david@kernel.org dwmw2@infradead.org itazur@amazon.com jackmanb@google.com kalyazin@amazon.com kvm@vger.kernel.org patrick.roy@campus.lmu.de pbonzini@redhat.com pdurrant@amazon.com seanjc@google.com tabba@google.com vkuznets@redhat.com zulinx86@gmail.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
next reply other threads:[~2026-03-10 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 13:38 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-27 6:28 [moderation/CI] Re: KVM: pfncache: Add guest_memfd support to pfncache syzbot ci
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=69b01ed5.a70a0220.be77.0114.GAE@google.com \
--to=syzbot+ci0d589002099e63f1@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