From: syzbot ci <syzbot+ci5dc234ac33873714@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: KVM: pfncache: Support guest_memfd without direct map
Date: Wed, 03 Dec 2025 07:31:22 -0800 [thread overview]
Message-ID: <693057ca.a70a0220.d98e3.01b7.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] KVM: pfncache: Support guest_memfd without direct map
https://lore.kernel.org/all/20251203144159.6131-1-itazur@amazon.com
* [RFC PATCH 1/2] KVM: pfncache: Use kvm_gmem_get_pfn() for guest_memfd-backed memslots
* [RFC PATCH 2/2] KVM: pfncache: Use vmap() for guest_memfd pages without direct map
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/c7f05710-e693-4b72-b1f1-3cf2bae8ac96
***
kernel build error
tree: kvm-next
URL: https://kernel.googlesource.com/pub/scm/virt/kvm/kvm/
base: 6b36119b94d0b2bb8cea9d512017efafd461d6ac
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/a42d2c64-c758-42f9-9dac-acd528bb662e/config
./include/linux/kvm_host.h:634:9: 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
reply other threads:[~2025-12-03 15:31 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=693057ca.a70a0220.d98e3.01b7.GAE@google.com \
--to=syzbot+ci5dc234ac33873714@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