From: Harry Yoo <harry.yoo@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the mm-hotfixes tree
Date: Thu, 21 Aug 2025 18:49:22 +0900 [thread overview]
Message-ID: <aKbroo3zVidG0YdK@hyeyoo> (raw)
In-Reply-To: <20250821160515.611d191e@canb.auug.org.au>
On Thu, Aug 21, 2025 at 04:05:15PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mm-hotfixes tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> ld: mm/kasan/init.o:(.toc+0x0): undefined reference to `kasan_early_shadow_p4d'
>
> Caused by commit
>
> 4b99d7a3e69a ("mm: introduce and use {pgd,p4d}_populate_kernel()")
>
> I have reverted that commit (and the following 07cf1bc1f659) for today.
Hi Stephen, thanks for reporting the build error.
I've sent a fix for it [1], and hopefully we can add it to mm-hotfixes soon.
[1] https://lore.kernel.org/linux-mm/20250821093542.37844-1-harry.yoo@oracle.com
--
Cheers,
Harry / Hyeonggon
next prev parent reply other threads:[~2025-08-21 9:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 6:05 linux-next: build failure after merge of the mm-hotfixes tree Stephen Rothwell
2025-08-21 9:49 ` Harry Yoo [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-21 12:59 Mark Brown
2026-04-21 13:06 ` David Hildenbrand (Arm)
2026-04-21 13:21 ` Mark Brown
2026-04-21 13:28 ` David Hildenbrand (Arm)
2026-04-21 13:34 ` Mark Brown
2026-04-21 13:42 ` David Hildenbrand (Arm)
2026-04-21 14:17 ` Andrew Morton
2026-04-21 14:20 ` David Hildenbrand (Arm)
2026-04-21 14:28 ` Andrew Morton
2026-04-21 14:35 ` David Hildenbrand (Arm)
2026-04-21 14:48 ` Andrew Morton
2026-04-21 15:04 ` David Hildenbrand (Arm)
2026-04-21 16:04 ` Philip Li
2026-04-21 16:21 ` David Hildenbrand (Arm)
2026-04-21 14:28 ` Mark Brown
2026-04-21 14:39 ` David Hildenbrand (Arm)
2025-12-07 21:35 Stephen Rothwell
2025-12-08 10:30 ` Maciej Wieczor-Retman
2025-12-09 1:37 ` Andrew Morton
2025-05-28 23:59 Stephen Rothwell
2025-05-29 0:02 ` Andrew Morton
2025-05-29 1:57 ` Stephen Rothwell
2025-05-29 0:03 ` Stephen Rothwell
2024-07-01 0:16 Stephen Rothwell
2024-07-01 1:01 ` Stephen Rothwell
2024-07-01 18:15 ` Yang Shi
2024-07-02 22:44 ` Stephen Rothwell
2024-07-02 23:22 ` Stephen Rothwell
2024-07-03 0:40 ` Yang Shi
2023-12-13 22:18 Stephen Rothwell
2023-12-13 23:31 ` Liam R. Howlett
2022-12-12 22:30 Stephen Rothwell
2022-12-13 1:34 ` Kefeng Wang
2022-12-13 2:23 ` Andrew Morton
2022-12-13 2:45 ` Stephen Rothwell
2022-12-13 2:54 ` Kefeng Wang
2022-11-25 1:10 Stephen Rothwell
2022-11-25 5:24 ` Juergen Gross
2022-11-25 5:24 ` Andrew Morton
2022-11-25 5:48 ` Stephen Rothwell
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=aKbroo3zVidG0YdK@hyeyoo \
--to=harry.yoo@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.