5.10 kernel series fails to build on newer toolchain: FAILED unresolved symbol filp_close
For some odd reason 5.10 kernel series doesn't compile with a newer toolchain since 2025-02-09:
2025-02-09T17:32:07.7991299Z GEN .version 2025-02-09T17:32:07.8270062Z CHK include/generated/compile.h 2025-02-09T17:32:07.8540777Z LD vmlinux.o 2025-02-09T17:32:11.7210899Z MODPOST vmlinux.symvers 2025-02-09T17:32:12.0869599Z MODINFO modules.builtin.modinfo 2025-02-09T17:32:12.1403022Z GEN modules.builtin 2025-02-09T17:32:12.1475659Z LD .tmp_vmlinux.btf 2025-02-09T17:32:19.6117204Z BTF .btf.vmlinux.bin.o 2025-02-09T17:32:31.2916650Z LD .tmp_vmlinux.kallsyms1 2025-02-09T17:32:34.8731104Z KSYMS .tmp_vmlinux.kallsyms1.S 2025-02-09T17:32:35.4910608Z AS .tmp_vmlinux.kallsyms1.o 2025-02-09T17:32:35.9662538Z LD .tmp_vmlinux.kallsyms2 2025-02-09T17:32:39.2595984Z KSYMS .tmp_vmlinux.kallsyms2.S 2025-02-09T17:32:39.8802028Z AS .tmp_vmlinux.kallsyms2.o 2025-02-09T17:32:40.3659440Z LD vmlinux 2025-02-09T17:32:48.0031558Z BTFIDS vmlinux 2025-02-09T17:32:48.0143553Z FAILED unresolved symbol filp_close 2025-02-09T17:32:48.5019928Z make: *** [Makefile:1207: vmlinux] Error 255 2025-02-09T17:32:48.5061241Z ==> ERROR: A failure occurred in build().
5.10.234 built fine couple of days ago with the older one. There were slight changes made. 5.4 and 5.15 still compile.
Wonder what might be missing here ...
On Fri, Mar 14, 2025 at 08:18:27AM +0700, Philip Müller wrote:
For some odd reason 5.10 kernel series doesn't compile with a newer toolchain since 2025-02-09:
2025-02-09T17:32:07.7991299Z GEN .version 2025-02-09T17:32:07.8270062Z CHK include/generated/compile.h 2025-02-09T17:32:07.8540777Z LD vmlinux.o 2025-02-09T17:32:11.7210899Z MODPOST vmlinux.symvers 2025-02-09T17:32:12.0869599Z MODINFO modules.builtin.modinfo 2025-02-09T17:32:12.1403022Z GEN modules.builtin 2025-02-09T17:32:12.1475659Z LD .tmp_vmlinux.btf 2025-02-09T17:32:19.6117204Z BTF .btf.vmlinux.bin.o 2025-02-09T17:32:31.2916650Z LD .tmp_vmlinux.kallsyms1 2025-02-09T17:32:34.8731104Z KSYMS .tmp_vmlinux.kallsyms1.S 2025-02-09T17:32:35.4910608Z AS .tmp_vmlinux.kallsyms1.o 2025-02-09T17:32:35.9662538Z LD .tmp_vmlinux.kallsyms2 2025-02-09T17:32:39.2595984Z KSYMS .tmp_vmlinux.kallsyms2.S 2025-02-09T17:32:39.8802028Z AS .tmp_vmlinux.kallsyms2.o 2025-02-09T17:32:40.3659440Z LD vmlinux 2025-02-09T17:32:48.0031558Z BTFIDS vmlinux 2025-02-09T17:32:48.0143553Z FAILED unresolved symbol filp_close 2025-02-09T17:32:48.5019928Z make: *** [Makefile:1207: vmlinux] Error 255 2025-02-09T17:32:48.5061241Z ==> ERROR: A failure occurred in build().
5.10.234 built fine couple of days ago with the older one. There were slight changes made. 5.4 and 5.15 still compile.
Wonder what might be missing here ...
Can you bisect down to the offending commit?
And I think I saw kernelci hit this as well, but I don't have an answer for it...
greg k-h
On 14/3/25 12:39, Greg Kroah-Hartman wrote:
Can you bisect down to the offending commit?
And I think I saw kernelci hit this as well, but I don't have an answer for it...
The same kernel compiles fine with the older toolchain. No changes were made to config nor patch-set when we tried to recompile the 5.10.234 kernel with the newer toolchain. 5.10.235 fails similar to 5.10.234 on the same toolchain.
So maybe a commit is missing, which is present in either 5.4 or 5.15 series.
Hello,
On Fri, 14 Mar 2025 16:19:13 +0700, Philip Müller wrote:
On 14/3/25 12:39, Greg Kroah-Hartman wrote:
Can you bisect down to the offending commit?
And I think I saw kernelci hit this as well, but I don't have an answer for it...
The same kernel compiles fine with the older toolchain. No changes were made to config nor patch-set when we tried to recompile the 5.10.234 kernel with the newer toolchain. 5.10.235 fails similar to 5.10.234 on the same toolchain.
So maybe a commit is missing, which is present in either 5.4 or 5.15 series.
KernelCI is now reporting a pass on the stable-rc build (5.10.236-rc1), though I was not able to spot exactly what fixed this.
Best, Laura
On Thu, Mar 20, 2025 at 12:28:06PM +0100, Laura Nao wrote:
Hello,
On Fri, 14 Mar 2025 16:19:13 +0700, Philip Müller wrote:
On 14/3/25 12:39, Greg Kroah-Hartman wrote:
Can you bisect down to the offending commit?
And I think I saw kernelci hit this as well, but I don't have an answer for it...
The same kernel compiles fine with the older toolchain. No changes were made to config nor patch-set when we tried to recompile the 5.10.234 kernel with the newer toolchain. 5.10.235 fails similar to 5.10.234 on the same toolchain.
So maybe a commit is missing, which is present in either 5.4 or 5.15 series.
KernelCI is now reporting a pass on the stable-rc build (5.10.236-rc1), though I was not able to spot exactly what fixed this.
That's good to know, thanks!
Yes, I can confirm that with the current stable-queue patches on top of 5.10.235 it compiles. I only had to not apply the following patch
ASoC: Intel: sof_sdw: Add support for Fatcat board with BT offload enabled in PTL platform
due to this compile error it created:
2025-03-28T08:55:34.9654713Z CC net/unix/sysctl_net_unix.o 2025-03-28T08:55:35.0056914Z sound/soc/intel/boards/sof_sdw.c:243:41: error: ‘SOC_SDW_PCH_DMIC’ undeclared here (not in a function); did you mean ‘SOF_SDW_PCH_DMIC’? 2025-03-28T08:55:35.0058317Z 243 | .driver_data = (void *)(SOC_SDW_PCH_DMIC | 2025-03-28T08:55:35.0059209Z | ^~~~~~~~~~~~~~~~ 2025-03-28T08:55:35.0060110Z | SOF_SDW_PCH_DMIC 2025-03-28T08:55:35.0578564Z sound/soc/intel/boards/sof_sdw.c:244:41: error: implicit declaration of function ‘SOF_BT_OFFLOAD_SSP’ [-Werror=implicit-function-declaration] 2025-03-28T08:55:35.0580183Z 244 | SOF_BT_OFFLOAD_SSP(2) | 2025-03-28T08:55:35.0581143Z | ^~~~~~~~~~~~~~~~~~ 2025-03-28T08:55:35.1499457Z sound/soc/intel/boards/sof_sdw.c:245:41: error: ‘SOF_SSP_BT_OFFLOAD_PRESENT’ undeclared here (not in a function) 2025-03-28T08:55:35.1500818Z 245 | SOF_SSP_BT_OFFLOAD_PRESENT), 2025-03-28T08:55:35.1501765Z | ^~~~~~~~~~~~~~~~~~~~~~~~~~ 2025-03-28T08:55:35.2672363Z cc1: some warnings being treated as errors 2025-03-28T08:55:35.2740103Z make[4]: *** [scripts/Makefile.build:286: sound/soc/intel/boards/sof_sdw.o] Error 1 2025-03-28T08:55:35.2767794Z make[3]: *** [scripts/Makefile.build:503: sound/soc/intel/boards] Error 2 2025-03-28T08:55:35.2773462Z make[2]: *** [scripts/Makefile.build:503: sound/soc/intel] Error 2 2025-03-28T08:55:35.2801723Z make[1]: *** [scripts/Makefile.build:503: sound/soc] Error 2 2025-03-28T08:55:35.2802890Z make: *** [Makefile:1837: sound] Error 2
On 3/20/25 07:28, Laura Nao wrote:
Hello,
On Fri, 14 Mar 2025 16:19:13 +0700, Philip Müller wrote:
On 14/3/25 12:39, Greg Kroah-Hartman wrote:
Can you bisect down to the offending commit?
And I think I saw kernelci hit this as well, but I don't have an answer for it...
The same kernel compiles fine with the older toolchain. No changes were made to config nor patch-set when we tried to recompile the 5.10.234 kernel with the newer toolchain. 5.10.235 fails similar to 5.10.234 on the same toolchain.
So maybe a commit is missing, which is present in either 5.4 or 5.15 series.
KernelCI is now reporting a pass on the stable-rc build (5.10.236-rc1), though I was not able to spot exactly what fixed this.
Best, Laura
On Fri, Mar 28, 2025 at 07:06:10AM -0400, Philip Müller wrote:
Yes, I can confirm that with the current stable-queue patches on top of 5.10.235 it compiles. I only had to not apply the following patch
ASoC: Intel: sof_sdw: Add support for Fatcat board with BT offload enabled in PTL platform
I've dropped this commit from the queue now, thanks.
greg k-h
linux-stable-mirror@lists.linaro.org
-
Greg KH -
Greg Kroah-Hartman
-
Laura Nao -
Philip Müller