From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>,
Ben Copeland <benjamin.copeland@linaro.org>
Subject: Re: [PATCH 5.15 000/387] 5.15.197-rc2 review
Date: Fri, 5 Dec 2025 19:04:01 +0100 [thread overview]
Message-ID: <2025120546-booted-twins-04bc@gregkh> (raw)
In-Reply-To: <20251205173947.GA2484770@ax162>
On Fri, Dec 05, 2025 at 10:39:47AM -0700, Nathan Chancellor wrote:
> On Fri, Dec 05, 2025 at 05:33:19PM +0100, Greg Kroah-Hartman wrote:
> > On Fri, Dec 05, 2025 at 12:59:37PM +0530, Naresh Kamboju wrote:
> > > On Thu, 4 Dec 2025 at 22:14, Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > This is the start of the stable review cycle for the 5.15.197 release.
> > > > There are 387 patches in this series, all will be posted as a response
> > > > to this one. If anyone has any issues with these being applied, please
> > > > let me know.
> > > >
> > > > Responses should be made by Sat, 06 Dec 2025 16:37:24 +0000.
> > > > Anything received after that time might be too late.
> > > >
> > > > The whole patch series can be found in one patch at:
> > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.197-rc2.gz
> > > > or in the git tree and branch at:
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
> > > > and the diffstat can be found below.
> > > >
> > > > thanks,
> > > >
> > > > greg k-h
> > >
> > >
> > > The powerpc allnoconfig failed with gcc-8 but passed with gcc-12.
> > >
> > > Build regression: powerpc: allnoconfig: gcc-8: Inconsistent kallsyms data
> > >
> > > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > >
> > > ### Build error Powerpc
> > > Inconsistent kallsyms data
> > > Try make KALLSYMS_EXTRA_PASS=1 as a workaround
> > > make[1]: *** [Makefile:1244: vmlinux] Error 1
> > >
> > > ### Commit pointing to,
> > > Makefile.compiler: replace cc-ifversion with compiler-specific macros
> > > commit 88b61e3bff93f99712718db785b4aa0c1165f35c upstream.
> > >
> > > ### Build
> > > - https://storage.tuxsuite.com/public/linaro/lkft/builds/36OCnVeYGpKUCXtxVdz6gezHjcQ/
> > > - https://storage.tuxsuite.com/public/linaro/lkft/builds/36OCnVeYGpKUCXtxVdz6gezHjcQ/config
> > >
> > > ### Steps to reproduce
> > > - tuxmake --runtime podman --target-arch powerpc --toolchain gcc-8
> > > --kconfig allnoconfig
> >
> > Odd, this works on 5.10 ok? What is different about 5.15 that keeps
> > this from working?
>
> This issue does reproduce for me locally but only with gcc-8 from TuxMake (i.e., a
> version from Debian), not with GCC 8.5.0 from kernel.org.
>
> $ git show -s --pretty=kernel
> 869807d760ee ("libbpf: Fix invalid return address register in s390")
>
> $ tuxmake -r podman -a powerpc -t gcc-8 -k allnoconfig default
> ...
> Inconsistent kallsyms data
> Try make KALLSYMS_EXTRA_PASS=1 as a workaround
> ...
>
> However, reverting the backport of 88b61e3bff93 ("Makefile.compiler:
> replace cc-ifversion with compiler-specific macros") does not resolve
> the issue for me:
>
> $ git revert --no-edit c8dad7eb1e6221e0363ee468dc46700bfbad6dd2
> [detached HEAD 1669da6455e4] Revert "Makefile.compiler: replace cc-ifversion with compiler-specific macros"
> Date: Fri Dec 5 10:30:10 2025 -0700
> 13 files changed, 30 insertions(+), 37 deletions(-)
>
> $ tuxmake -r podman -a powerpc -t gcc-8 -k allnoconfig default
> ...
> Inconsistent kallsyms data
> Try make KALLSYMS_EXTRA_PASS=1 as a workaround
> ...
>
> My bisect landed on the backport of 19de03b312d6 ("block: make
> REQ_OP_ZONE_OPEN a write operation") and reverting that actually
> resolves the error.
>
> $ git bisect log
> # bad: [869807d760eeef0e0132eed3f1be6be16d084401] libbpf: Fix invalid return address register in s390
> # good: [cc5ec87693063acebb60f587e8a019ba9b94ae0e] Linux 5.15.196
> git bisect start '869807d760eeef0e0132eed3f1be6be16d084401' 'cc5ec87693063acebb60f587e8a019ba9b94ae0e'
> # bad: [ffd15ced026694355243064968a3b84269e0ee09] ARM: at91: pm: save and restore ACR during PLL disable/enable
> git bisect bad ffd15ced026694355243064968a3b84269e0ee09
> # bad: [1ba52b54e5f45e982d61b4eeabbf28d78a5f9e75] drm/amdkfd: return -ENOTTY for unsupported IOCTLs
> git bisect bad 1ba52b54e5f45e982d61b4eeabbf28d78a5f9e75
> # good: [8966a057d07281a5e65eaa3225cb072713921b25] Revert "docs/process/howto: Replace C89 with C11"
> git bisect good 8966a057d07281a5e65eaa3225cb072713921b25
> # bad: [27df52e05f7dd606e18e869cb4f52ce1fbfe699f] tee: allow a driver to allocate a tee_device without a pool
> git bisect bad 27df52e05f7dd606e18e869cb4f52ce1fbfe699f
> # bad: [2b426fa49ef76bbe04671b3a861352b924a01b96] memstick: Add timeout to prevent indefinite waiting
> git bisect bad 2b426fa49ef76bbe04671b3a861352b924a01b96
> # bad: [c126c39dc662661531c96acbbf5fc129ed7f535a] soc: qcom: smem: Fix endian-unaware access of num_entries
> git bisect bad c126c39dc662661531c96acbbf5fc129ed7f535a
> # good: [c142f0d16766ab7189af4b9128a2c81c56f7a01f] drm/sysfb: Do not dereference NULL pointer in plane reset
> git bisect good c142f0d16766ab7189af4b9128a2c81c56f7a01f
> # bad: [02dc541fc61c3e2dabc3574fe46a19f554ea5d8c] soc: aspeed: socinfo: Add AST27xx silicon IDs
> git bisect bad 02dc541fc61c3e2dabc3574fe46a19f554ea5d8c
> # bad: [23e0fecb7be5010e96b2948490799ef59ac4bea6] block: make REQ_OP_ZONE_OPEN a write operation
> git bisect bad 23e0fecb7be5010e96b2948490799ef59ac4bea6
> # first bad commit: [23e0fecb7be5010e96b2948490799ef59ac4bea6] block: make REQ_OP_ZONE_OPEN a write operation
>
> $ git revert --no-edit 23e0fecb7be5010e96b2948490799ef59ac4bea6
> [detached HEAD ddf3a34910b0] Revert "block: make REQ_OP_ZONE_OPEN a write operation"
> Date: Fri Dec 5 10:26:26 2025 -0700
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> $ tuxmake -r podman -a powerpc -t gcc-8 -k allnoconfig default
> ...
> I: config: PASS in 0:00:01.410526
> I: default: PASS in 0:00:04.933923
> ...
>
> No idea why that commit would cause such an issue... but it does not
> appear to be 88b61e3bff93 so I guess I am off the hook ;)
Great, thanks for looking into this and the information. I'll leave
your patch in :)
greg k-h
next prev parent reply other threads:[~2025-12-05 18:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 16:44 [PATCH 5.15 000/387] 5.15.197-rc2 review Greg Kroah-Hartman
2025-12-04 23:45 ` Mark Brown
2025-12-05 7:29 ` Naresh Kamboju
2025-12-05 16:33 ` Greg Kroah-Hartman
2025-12-05 17:19 ` Guenter Roeck
2025-12-05 17:39 ` Nathan Chancellor
2025-12-05 18:04 ` Greg Kroah-Hartman [this message]
2025-12-05 18:31 ` Guenter Roeck
2025-12-05 10:58 ` Jon Hunter
2025-12-05 11:14 ` Brett A C Sheffield
2025-12-05 17:37 ` Florian Fainelli
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=2025120546-booted-twins-04bc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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