From: Salvatore Bonaccorso <carnil@debian.org>
To: stable@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
Aboorva Devarajan <aboorvad@linux.ibm.com>,
ritesh.list@gmail.com, hbathini@linux.ibm.com,
mpe@ellerman.id.au, regressions@lists.linux.dev, benh@debian.org
Subject: [regression 6.1.y] Backport of 353d7a84c214f18 ("powerpc/64s/radix/kfence: map __kfence_pool at page granularity") to stable versions 6.1 causes build failure
Date: Fri, 16 Jan 2026 21:56:44 +0100 [thread overview]
Message-ID: <aWqmDHdHVLs5M3HQ@eldamar.lan> (raw)
Hi,
In v6.1.160 353d7a84c214f18 ("powerpc/64s/radix/kfence: map
__kfence_pool at page granularity") was backported. But this now
causes a build failure:
make KERNELRELEASE=6.1.159+ ARCH=powerpc KBUILD_BUILD_VERSION=3 -f ./Makefile
CALL scripts/checksyscalls.sh
UPD init/utsversion-tmp.h
CC init/version.o
AR init/built-in.a
CC arch/powerpc/mm/book3s64/radix_pgtable.o
In file included from arch/powerpc/mm/book3s64/radix_pgtable.c:35:
./arch/powerpc/include/asm/kfence.h: In function 'kfence_protect_page':
./arch/powerpc/include/asm/kfence.h:37:9: error: implicit declaration of function '__kernel_map_pages'; did you mean 'hash__kernel_map_pages'? [-Werror=implicit-function-declaration]
37 | __kernel_map_pages(page, 1, !protect);
| ^~~~~~~~~~~~~~~~~~
| hash__kernel_map_pages
cc1: some warnings being treated as errors
make[7]: *** [scripts/Makefile.build:250: arch/powerpc/mm/book3s64/radix_pgtable.o] Error 1
make[6]: *** [scripts/Makefile.build:503: arch/powerpc/mm/book3s64] Error 2
This is because 8f14a96386b2 ("mm: page_poison: always declare
__kernel_map_pages() function") is missing from 6.1.y (it was only
included in 6.5-rc1).
Cherry-picking 8f14a96386b2 fixes the build failure on powerpc.
#regzbot introduced 36c1dc122eb3b917cd2c343029ff60a366a00539
Marking as regression for 36c1dc122eb3 ("powerpc/64s/radix/kfence: map
__kfence_pool at page granularity"), for the 6.1.y specific commit
causing the regression.
Regards,
Salvatore
next reply other threads:[~2026-01-16 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 20:56 Salvatore Bonaccorso [this message]
2026-01-17 15:39 ` [regression 6.1.y] Backport of 353d7a84c214f18 ("powerpc/64s/radix/kfence: map __kfence_pool at page granularity") to stable versions 6.1 causes build failure Greg Kroah-Hartman
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=aWqmDHdHVLs5M3HQ@eldamar.lan \
--to=carnil@debian.org \
--cc=aboorvad@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=benh@debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=hbathini@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=regressions@lists.linux.dev \
--cc=ritesh.list@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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