From: LEROY Christophe <christophe.leroy2@cs-soprasteria.com>
To: Erhard Furtner <erhard_f@mailbox.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Suren Baghdasaryan <surenb@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Kernel build failure with MEM_ALLOC_PROFILING=y set (Talos II, v6.10-rc5)
Date: Thu, 22 Aug 2024 17:18:36 +0000 [thread overview]
Message-ID: <b5ae7797-7676-4abf-82be-e2ce4d9238a1@cs-soprasteria.com> (raw)
In-Reply-To: <20240721010926.60efacc3@yea>
Le 21/07/2024 à 01:09, Erhard Furtner a écrit :
> [Vous ne recevez pas souvent de courriers de erhard_f@mailbox.org. D?couvrez pourquoi ceci est important ? https://aka.ms/LearnAboutSenderIdentification ]
>
> 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.
>
I guess those three functions are missing EXPORT_SYMBOL_GPL() tagging.
Christophe
next parent reply other threads:[~2024-08-22 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240629153128.4660755c@yea>
[not found] ` <20240721010926.60efacc3@yea>
2024-08-22 17:18 ` LEROY Christophe [this message]
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=b5ae7797-7676-4abf-82be-e2ce4d9238a1@cs-soprasteria.com \
--to=christophe.leroy2@cs-soprasteria.com \
--cc=akpm@linux-foundation.org \
--cc=erhard_f@mailbox.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=surenb@google.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