All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: stable@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	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: Re: [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: Sat, 17 Jan 2026 16:39:11 +0100	[thread overview]
Message-ID: <2026011705-turbulent-scheme-71ef@gregkh> (raw)
In-Reply-To: <aWqmDHdHVLs5M3HQ@eldamar.lan>

On Fri, Jan 16, 2026 at 09:56:44PM +0100, Salvatore Bonaccorso wrote:
> 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.

Now queued up, thanks.

greg k-h

      reply	other threads:[~2026-01-17 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 20:56 [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 Salvatore Bonaccorso
2026-01-17 15:39 ` Greg Kroah-Hartman [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=2026011705-turbulent-scheme-71ef@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=aboorvad@linux.ibm.com \
    --cc=arnd@arndb.de \
    --cc=benh@debian.org \
    --cc=carnil@debian.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 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.