From: Suren Baghdasaryan <surenb@google.com>
To: LEROY Christophe <christophe.leroy2@cs-soprasteria.com>
Cc: Erhard Furtner <erhard_f@mailbox.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Andrew Morton <akpm@linux-foundation.org>,
"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 11:25:52 -0700 [thread overview]
Message-ID: <CAJuCfpGDzaW9mA3TYxFJ0y6kM7bvNt0wbBy_vRdmN+pRGFNfQg@mail.gmail.com> (raw)
In-Reply-To: <CAJuCfpH9e0zvrBK8A_TEHO=maHqijjPcC21=To7VU-mmp0ZYBQ@mail.gmail.com>
On Thu, Aug 22, 2024 at 11:04 AM Suren Baghdasaryan <surenb@google.com> wrote:
>
> On Thu, Aug 22, 2024 at 10:18 AM LEROY Christophe
> <christophe.leroy2@cs-soprasteria.com> wrote:
> >
> >
> >
> > 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.
>
> The issue should have been fixed by
> https://lore.kernel.org/all/20240717181239.2510054-1-surenb@google.com/
> patchset. I probably forgot to CC stable@ for these changes. Let me
> check and follow up.
The issue is fixed by the patch titled "alloc_tag: outline and export
free_reserved_page()" which has b3bebe44306e SHA in Linus' tree and
first appears in v6.10.3 with SHA 4a9a52b70cce.
> Thanks,
> Suren.
>
> >
> > Christophe
prev parent reply other threads:[~2024-08-22 18:26 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
2024-08-22 18:04 ` Suren Baghdasaryan
2024-08-22 18:25 ` Suren Baghdasaryan [this message]
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=CAJuCfpGDzaW9mA3TYxFJ0y6kM7bvNt0wbBy_vRdmN+pRGFNfQg@mail.gmail.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy2@cs-soprasteria.com \
--cc=erhard_f@mailbox.org \
--cc=linux-mm@kvack.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