[moderation/CI] Re: kernel: Introduce multikernel architecture support

[moderation/CI] Re: kernel: Introduce multikernel architecture support

[syzbot ci]

syzbot ci has tested the following series

[v1] kernel: Introduce multikernel architecture support
https://lore.kernel.org/all/20250918222607.186488-1-xiyou.wangcong@gmail.com
* [RFC Patch 1/7] kexec: Introduce multikernel support via kexec
* [RFC Patch 2/7] x86: Introduce SMP INIT trampoline for multikernel CPU bootstrap
* [RFC Patch 3/7] x86: Introduce MULTIKERNEL_VECTOR for inter-kernel communication
* [RFC Patch 4/7] kernel: Introduce generic multikernel IPI communication framework
* [RFC Patch 5/7] x86: Introduce arch_cpu_physical_id() to obtain physical CPU ID
* [RFC Patch 6/7] kexec: Implement dynamic kimage tracking
* [RFC Patch 7/7] kexec: Add /proc/multikernel interface for kimage tracking

and found the following issue:
WARNING in note_page

Full report is available here:
https://ci.syzbot.org/series/9ca759c7-776a-4d45-a2f9-5e6ca245e989

***

WARNING in note_page

tree:      torvalds
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base:      f83ec76bf285bea5727f478a68b894f5543ca76e
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/645f543b-aa06-4977-81f2-45a0b44a2133/config

Key type fscrypt-provisioning registered
kAFS: Red Hat AFS client v0.1 registering.
Btrfs loaded, assert=on, ref-verify=on, zoned=yes, fsverity=yes
Key type big_key registered
Key type encrypted registered
AppArmor: AppArmor sha256 policy hashing enabled
ima: No TPM chip found, activating TPM-bypass!
Loading compiled-in module X.509 certificates
Loaded X.509 cert 'Build time autogenerated kernel key: 75e3f237904f24df4a2b6e4eae1a8f34effb6643'
ima: Allocated hash algorithm: sha256
ima: No architecture policies found
evm: Initialising EVM extended attributes:
evm: security.selinux (disabled)
evm: security.SMACK64 (disabled)
evm: security.SMACK64EXEC (disabled)
evm: security.SMACK64TRANSMUTE (disabled)
evm: security.SMACK64MMAP (disabled)
evm: security.apparmor
evm: security.ima
evm: security.capability
evm: HMAC attrs: 0x1
PM:   Magic number: 9:738:504
usb usb41-port1: hash matches
usb usb40-port2: hash matches
netconsole: network logging started
gtp: GTP module loaded (pdp ctx size 128 bytes)
rdma_rxe: loaded
cfg80211: Loading compiled-in X.509 certificates for regulatory database
Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
clk: Disabling unused clocks
ALSA device list:
  #0: Dummy 1
  #1: Loopback 1
  #2: Virtual MIDI Card 1
check access for rdinit=/init failed: -2, ignoring
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT4-fs (sda1): mounted filesystem b4773fba-1738-4da0-8a90-0fe043d0a496 ro with ordered data mode. Quota mode: none.
VFS: Mounted root (ext4 filesystem) readonly on device 8:1.
devtmpfs: mounted
Freeing unused kernel image (initmem) memory: 26168K
Write protecting the kernel read-only data: 210944k
Freeing unused kernel image (text/rodata gap) memory: 104K
Freeing unused kernel image (rodata/data gap) memory: 300K
------------[ cut here ]------------
x86/mm: Found insecure W+X mapping at address 0xffff888000096000
WARNING: CPU: 1 PID: 1 at arch/x86/mm/dump_pagetables.c:248 note_page+0x12a5/0x14a0
Modules linked in:
CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:note_page+0x12a5/0x14a0
Code: d5 49 00 c6 05 bd 7d 17 0e 01 90 43 80 3c 2e 00 74 08 4c 89 ff e8 9b 47 ad 00 49 8b 37 48 c7 c7 40 98 88 8b e8 1c 53 0d 00 90 <0f> 0b 90 90 49 bd 00 00 00 00 00 fc ff df e9 5a f1 ff ff 44 89 f9
RSP: 0000:ffffc90000047678 EFLAGS: 00010246
RAX: 0829288c8ce4fa00 RBX: ffffc90000047cf0 RCX: ffff88801c2d0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: 0000000000000001 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1bfa274 R12: ffffffffffffffff
R13: dffffc0000000000 R14: 1ffff92000008fb2 R15: ffffc90000047d90
FS:  0000000000000000(0000) GS:ffff8881a3c09000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000df36000 CR4: 00000000000006f0
Call Trace:
 <TASK>
 ptdump_pte_entry+0xc6/0xe0
 walk_pte_range_inner+0x1ba/0x380
 walk_pgd_range+0x1467/0x1d40
 walk_page_range_debug+0x312/0x3d0
 ptdump_walk_pgd+0x126/0x320
 ptdump_walk_pgd_level_core+0x260/0x3e0
 kernel_init+0x53/0x1d0
 ret_from_fork+0x439/0x7d0
 ret_from_fork_asm+0x1a/0x30
 </TASK>


***

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:
[akpm@linux-foundation.org bhe@redhat.com changyuanl@google.com cwang@multikernel.io graf@amazon.com kexec@lists.infradead.org linux-kernel@vger.kernel.org linux-mm@kvack.org pasha.tatashin@soleen.com rppt@kernel.org xiyou.wangcong@gmail.com]

If the report looks fine to you, reply with:
#syz upstream

Re: [moderation/CI] Re: kernel: Introduce multikernel architecture support

[Aleksandr Nogikh]

#syz upstream

On Fri, Sep 19, 2025 at 1:38 AM syzbot ci
<syzbot+cid1ab3854931cd1b5@syzkaller.appspotmail.com> wrote:
>
> syzbot ci has tested the following series
>
> [v1] kernel: Introduce multikernel architecture support
> https://lore.kernel.org/all/20250918222607.186488-1-xiyou.wangcong@gmail.com
> * [RFC Patch 1/7] kexec: Introduce multikernel support via kexec
> * [RFC Patch 2/7] x86: Introduce SMP INIT trampoline for multikernel CPU bootstrap
> * [RFC Patch 3/7] x86: Introduce MULTIKERNEL_VECTOR for inter-kernel communication
> * [RFC Patch 4/7] kernel: Introduce generic multikernel IPI communication framework
> * [RFC Patch 5/7] x86: Introduce arch_cpu_physical_id() to obtain physical CPU ID
> * [RFC Patch 6/7] kexec: Implement dynamic kimage tracking
> * [RFC Patch 7/7] kexec: Add /proc/multikernel interface for kimage tracking
>
> and found the following issue:
> WARNING in note_page
>
> Full report is available here:
> https://ci.syzbot.org/series/9ca759c7-776a-4d45-a2f9-5e6ca245e989
>
> ***
>
> WARNING in note_page
>
> tree:      torvalds
> URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
> base:      f83ec76bf285bea5727f478a68b894f5543ca76e
> 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/645f543b-aa06-4977-81f2-45a0b44a2133/config
>
> Key type fscrypt-provisioning registered
> kAFS: Red Hat AFS client v0.1 registering.
> Btrfs loaded, assert=on, ref-verify=on, zoned=yes, fsverity=yes
> Key type big_key registered
> Key type encrypted registered
> AppArmor: AppArmor sha256 policy hashing enabled
> ima: No TPM chip found, activating TPM-bypass!
> Loading compiled-in module X.509 certificates
> Loaded X.509 cert 'Build time autogenerated kernel key: 75e3f237904f24df4a2b6e4eae1a8f34effb6643'
> ima: Allocated hash algorithm: sha256
> ima: No architecture policies found
> evm: Initialising EVM extended attributes:
> evm: security.selinux (disabled)
> evm: security.SMACK64 (disabled)
> evm: security.SMACK64EXEC (disabled)
> evm: security.SMACK64TRANSMUTE (disabled)
> evm: security.SMACK64MMAP (disabled)
> evm: security.apparmor
> evm: security.ima
> evm: security.capability
> evm: HMAC attrs: 0x1
> PM:   Magic number: 9:738:504
> usb usb41-port1: hash matches
> usb usb40-port2: hash matches
> netconsole: network logging started
> gtp: GTP module loaded (pdp ctx size 128 bytes)
> rdma_rxe: loaded
> cfg80211: Loading compiled-in X.509 certificates for regulatory database
> Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
> clk: Disabling unused clocks
> ALSA device list:
>   #0: Dummy 1
>   #1: Loopback 1
>   #2: Virtual MIDI Card 1
> check access for rdinit=/init failed: -2, ignoring
> md: Waiting for all devices to be available before autodetect
> md: If you don't use raid, use raid=noautodetect
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> EXT4-fs (sda1): mounted filesystem b4773fba-1738-4da0-8a90-0fe043d0a496 ro with ordered data mode. Quota mode: none.
> VFS: Mounted root (ext4 filesystem) readonly on device 8:1.
> devtmpfs: mounted
> Freeing unused kernel image (initmem) memory: 26168K
> Write protecting the kernel read-only data: 210944k
> Freeing unused kernel image (text/rodata gap) memory: 104K
> Freeing unused kernel image (rodata/data gap) memory: 300K
> ------------[ cut here ]------------
> x86/mm: Found insecure W+X mapping at address 0xffff888000096000
> WARNING: CPU: 1 PID: 1 at arch/x86/mm/dump_pagetables.c:248 note_page+0x12a5/0x14a0
> Modules linked in:
> CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> RIP: 0010:note_page+0x12a5/0x14a0
> Code: d5 49 00 c6 05 bd 7d 17 0e 01 90 43 80 3c 2e 00 74 08 4c 89 ff e8 9b 47 ad 00 49 8b 37 48 c7 c7 40 98 88 8b e8 1c 53 0d 00 90 <0f> 0b 90 90 49 bd 00 00 00 00 00 fc ff df e9 5a f1 ff ff 44 89 f9
> RSP: 0000:ffffc90000047678 EFLAGS: 00010246
> RAX: 0829288c8ce4fa00 RBX: ffffc90000047cf0 RCX: ffff88801c2d0000
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
> RBP: 0000000000000001 R08: 0000000000000003 R09: 0000000000000004
> R10: dffffc0000000000 R11: fffffbfff1bfa274 R12: ffffffffffffffff
> R13: dffffc0000000000 R14: 1ffff92000008fb2 R15: ffffc90000047d90
> FS:  0000000000000000(0000) GS:ffff8881a3c09000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000000000000 CR3: 000000000df36000 CR4: 00000000000006f0
> Call Trace:
>  <TASK>
>  ptdump_pte_entry+0xc6/0xe0
>  walk_pte_range_inner+0x1ba/0x380
>  walk_pgd_range+0x1467/0x1d40
>  walk_page_range_debug+0x312/0x3d0
>  ptdump_walk_pgd+0x126/0x320
>  ptdump_walk_pgd_level_core+0x260/0x3e0
>  kernel_init+0x53/0x1d0
>  ret_from_fork+0x439/0x7d0
>  ret_from_fork_asm+0x1a/0x30
>  </TASK>
>
>
> ***
>
> 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:
> [akpm@linux-foundation.org bhe@redhat.com changyuanl@google.com cwang@multikernel.io graf@amazon.com kexec@lists.infradead.org linux-kernel@vger.kernel.org linux-mm@kvack.org pasha.tatashin@soleen.com rppt@kernel.org xiyou.wangcong@gmail.com]
>
> If the report looks fine to you, reply with:
> #syz upstream
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-moderation+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/68cc97f9.050a0220.139b6.000b.GAE%40google.com.

[moderation/CI] Re: kernel: Introduce multikernel architecture support

[syzbot ci]

syzbot ci has tested the following series

[v2] kernel: Introduce multikernel architecture support
https://lore.kernel.org/all/20251019061631.2235405-1-xiyou.wangcong@gmail.com
* [RFC Patch v2 01/16] kexec: Introduce multikernel support via kexec
* [RFC Patch v2 02/16] x86: Introduce SMP INIT trampoline for multikernel CPU bootstrap
* [RFC Patch v2 03/16] multikernel: Introduce basic multikernel subsystem infrastructure
* [RFC Patch v2 04/16] x86: Introduce MULTIKERNEL_VECTOR for inter-kernel communication
* [RFC Patch v2 05/16] x86: Introduce arch_cpu_physical_id() to obtain physical CPU ID
* [RFC Patch v2 06/16] multikernel: Introduce physical memory reservation and allocation
* [RFC Patch v2 07/16] kexec: Implement dynamic kimage tracking
* [RFC Patch v2 08/16] multikernel: Introduce device-tree based kernfs interface
* [RFC Patch v2 09/16] kexec: Integrate multikernel instance management with kexec subsystem
* [RFC Patch v2 10/16] Documentation: Add multikernel usage
* [RFC Patch v2 11/16] kexec: Add /proc/kimage interface for kimage tracking
* [RFC Patch v2 12/16] multikernel: Introduce per-instance memory allocation interface
* [RFC Patch v2 13/16] kernel: Introduce generic multikernel IPI communication framework
* [RFC Patch v2 14/16] multikernel: Add messaging layer for inter-kernel communication
* [RFC Patch v2 15/16] kexec: Integrate multikernel support with kexec_file_load()
* [RFC Patch v2 16/16] multikernel: Integrate Kexec HandOver framework for DTB preservation

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/5e5f2222-c421-445c-80a8-329e052eb00d

***

kernel build error

tree:      torvalds
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base:      3a8660878839faadb4f1a6dd72c3179c1df56787
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/b83eab88-f300-46c6-99d0-d9ce6edaf4eb/config

ld.lld: error: undefined symbol: mk_kimage_alloc
ld.lld: error: undefined symbol: mk_kimage_free
ld.lld: error: undefined symbol: mk_instance_set_state
ld.lld: error: undefined symbol: mk_instance_put
ld.lld: error: undefined symbol: mk_instance_find

***

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:
[akpm@linux-foundation.org bhe@redhat.com changyuanl@google.com cwang@multiernel.io cwang@multikernel.io graf@amazon.com jiri@resnulli.us kexec@lists.infradead.org linux-kernel@vger.kernel.org linux-mm@kvack.org multikernel@lists.linux.dev pasha.tatashin@soleen.com rppt@kernel.org stefanha@redhat.com xiyou.wangcong@gmail.com]

If the report looks fine to you, reply with:
#syz upstream