From: Erhard Furtner <erhard_f@mailbox.org>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: Kernel build failure with MEM_ALLOC_PROFILING=y set (Talos II, v6.10-rc5)
Date: Sun, 21 Jul 2024 01:09:26 +0200 [thread overview]
Message-ID: <20240721010926.60efacc3@yea> (raw)
In-Reply-To: <20240629153128.4660755c@yea>
On Sat, 29 Jun 2024 15:31:28 +0200
Erhard Furtner <erhard_f@mailbox.org> wrote:
> I get a build failure on v6.10-rc5 on my Talos II when MEM_ALLOC_PROFILING=y is enabled:
>
> [...]
> LD [M] fs/xfs/xfs.o
> LD [M] fs/bcachefs/bcachefs.o
> AR built-in.a
> AR vmlinux.a
> LD vmlinux.o
> OBJCOPY modules.builtin.modinfo
> GEN modules.builtin
> GEN .vmlinux.objs
> MODPOST Module.symvers
> ERROR: modpost: "page_ext_get" [arch/powerpc/kvm/kvm-hv.ko] undefined!
> ERROR: modpost: "mem_alloc_profiling_key" [arch/powerpc/kvm/kvm-hv.ko] undefined!
> ERROR: modpost: "page_ext_put" [arch/powerpc/kvm/kvm-hv.ko] undefined!
> make[2]: *** [scripts/Makefile.modpost:145: Module.symvers] Fehler 1
> make[1]: *** [/usr/src/linux-stable/Makefile:1886: modpost] Fehler 2
> make: *** [Makefile:240: __sub-make] Fehler 2
>
> Same .config builds fine without MEM_ALLOC_PROFILING set. Kernel .config attached.
Build problem still there on now released v6.10 with MEM_ALLOC_PROFILING=y.
Can't bisect as build with MEM_ALLOC_PROFILING fails since it's introduction in v6.10-rc1.
Regards,
Erhard
next prev parent reply other threads:[~2024-07-20 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-29 13:31 Kernel build failure with MEM_ALLOC_PROFILING=y set (Talos II, v6.10-rc5) Erhard Furtner
2024-07-20 23:09 ` Erhard Furtner [this message]
2024-08-22 17:18 ` LEROY Christophe
2024-08-22 18:04 ` Suren Baghdasaryan
2024-08-22 18:25 ` Suren Baghdasaryan
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=20240721010926.60efacc3@yea \
--to=erhard_f@mailbox.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).