From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Philip Müller" <philm@manjaro.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: 5.10 kernel series fails to build on newer toolchain: FAILED unresolved symbol filp_close
Date: Fri, 14 Mar 2025 06:39:45 +0100 [thread overview]
Message-ID: <2025031408-dividers-alphabet-d26c@gregkh> (raw)
In-Reply-To: <b39ca723-16a4-42a2-b8ca-b97d0e4bf7f5@manjaro.org>
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
next prev parent reply other threads:[~2025-03-14 5:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 1:18 5.10 kernel series fails to build on newer toolchain: FAILED unresolved symbol filp_close Philip Müller
2025-03-14 5:39 ` Greg Kroah-Hartman [this message]
2025-03-14 9:19 ` Philip Müller
2025-03-20 11:28 ` Laura Nao
2025-03-20 12:55 ` Greg KH
2025-03-28 11:06 ` Philip Müller
2025-04-01 9:17 ` Greg KH
2025-06-05 7:44 ` Philip Müller
2025-06-05 8:46 ` Greg KH
2025-06-08 6:27 ` Philip Müller
2025-06-17 14:05 ` Greg KH
2025-06-19 8:34 ` Philip Müller
2025-06-19 8:47 ` Greg KH
2025-06-24 7:05 ` Philip Müller
2025-10-26 13:26 ` Alyssa Ross
2025-12-15 19:00 ` David Nyström
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=2025031408-dividers-alphabet-d26c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=philm@manjaro.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