Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci1e21bcc277045ad6@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mshv: enable kexec with Hyper-V donated pages and partitions
Date: Wed, 27 May 2026 23:00:34 -0700	[thread overview]
Message-ID: <6a17da02.d07c18fe.1069e4.001a.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] mshv: enable kexec with Hyper-V donated pages and partitions
https://lore.kernel.org/all/20260528004204.1484584-1-jloeser@linux.microsoft.com
* [RFC PATCH 01/20] kho: generalize radix tree APIs
* [RFC PATCH 02/20] kho: store incoming radix tree in kho_in
* [RFC PATCH 03/20] kho: add a struct for radix callbacks
* [RFC PATCH 04/20] kho: add callback for table pages
* [RFC PATCH 05/20] kho: add data argument to radix walk callback
* [RFC PATCH 06/20] kho: allow early-boot usage of the KHO radix tree
* [RFC PATCH 07/20] kho: allow destroying KHO radix tree
* [RFC PATCH 08/20] kho: add kho_radix_init_tree()
* [RFC PATCH 09/20] memblock: introduce MEMBLOCK_KHO_SCRATCH_EXT
* [RFC PATCH 10/20] kho: extended scratch
* [RFC PATCH 11/20] kho: return virtual address of mem_map
* [RFC PATCH 12/20] mm/hugetlb: make bootmem allocation work with KHO
* [RFC PATCH 13/20] kho: add radix tree freeze and del_key() error reporting
* [RFC PATCH 14/20] kho: Add crash-kernel-safe radix tree presence check
* [RFC PATCH 15/20] mshv: Use page tracker to manage MSHV-owned pages and preserve with KHO
* [RFC PATCH 16/20] mshv: Add debugfs interface to page tracker
* [RFC PATCH 17/20] hyperv: Reserve crash MSR P2 for page preservation root PA
* [RFC PATCH 18/20] mshv: Exclude Hyper-V donated pages from crash dump collection
* [RFC PATCH 19/20] kexec: export kexec_in_progress for modules
* [RFC PATCH 20/20] mshv: freeze and vacuum partitions across kexec

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/3ae14a59-1f75-49c7-b968-ba5197b42ec3

***

kernel build error

tree:      linux-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base:      e7d700e14934e68f86338c5610cf2ae76798b663
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/90866729-fbd8-4e80-afc5-b8813f0533fa/config

mm/mm_init.c:2705:2: error: call to undeclared function 'kho_extend_scratch'; 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.

To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[akpm@linux-foundation.org bhe@redhat.com bp@alien8.de catalin.marinas@arm.com dave.hansen@linux.intel.com david@kernel.org decui@microsoft.com graf@amazon.com haiyangz@microsoft.com hpa@zytor.com jasonmiu@google.com jbouron@amazon.com jloeser@linux.microsoft.com kees@kernel.org kexec@lists.infradead.org kys@microsoft.com linux-arm-kernel@lists.infradead.org linux-hyperv@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org longli@microsoft.com mario.limonciello@amd.com mhklinux@outlook.com mingo@redhat.com muchun.song@linux.dev osalvador@suse.de pasha.tatashin@soleen.com piliu@redhat.com pratyush@kernel.org rafael.j.wysocki@intel.com ran.xiaokai@zte.com.cn rppt@kernel.org sourabhjain@linux.ibm.com tglx@kernel.org wei.liu@kernel.org will@kernel.org x86@kernel.org]

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-05-28  6:00 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=6a17da02.d07c18fe.1069e4.001a.GAE@google.com \
    --to=syzbot+ci1e21bcc277045ad6@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