From: Greg KH <gregkh@linuxfoundation.org>
To: Laura Nao <laura.nao@collabora.com>
Cc: philm@manjaro.org, stable@vger.kernel.org
Subject: Re: 5.10 kernel series fails to build on newer toolchain: FAILED unresolved symbol filp_close
Date: Thu, 20 Mar 2025 05:55:17 -0700 [thread overview]
Message-ID: <2025032007-symptom-zero-8b17@gregkh> (raw)
In-Reply-To: <20250320112806.332385-1-laura.nao@collabora.com>
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!
next prev parent reply other threads:[~2025-03-20 12:56 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
2025-03-14 9:19 ` Philip Müller
2025-03-20 11:28 ` Laura Nao
2025-03-20 12:55 ` Greg KH [this message]
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=2025032007-symptom-zero-8b17@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=laura.nao@collabora.com \
--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 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.