From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Regression: commit 987fdfec2410 causes build to incorrectly issue warning
Date: Fri, 2 Jul 2021 15:48:33 +0100 [thread overview]
Message-ID: <20210702144833.GO22278@shell.armlinux.org.uk> (raw)
In-Reply-To: <20210702131301.GD1350@shell.armlinux.org.uk>
On Fri, Jul 02, 2021 at 02:13:01PM +0100, Russell King - ARM Linux admin wrote:
> Hi,
>
> Commit 987fdfec2410 ("arm64: move --fix-cortex-a53-843419 linker test to
> Kconfig") breaks the ability to detect linker support for this option.
> Building 5.13 for aarch64 with Debian binutils 2.31.1 results in:
>
> .../arch/arm64/Makefile:25: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum
>
> This is because ARM64_LD_HAS_FIX_ERRATUM_843419 is not set in the
> Kconfig, indicating that the Kconfig test for linker support for
> --fix-cortex-a53-843419 has failed, yet this version of binutils does
> support this option:
>
> $ aarch64-linux-gnu-ld --help | grep -e --fix-cortex-a53-843419 | wc -l
> 8
>
> Reverting this commit fixes the problem for me.
Sadly, while reverting the commit fixes it during the initial build
run, the warning pops up when doing the installation step.
I'm not entirely sure what's going on here. Having put the commit
back, and re-run strace (and waited ages) it appears that the
ld-option command does succeed, and I eventually end up with the
option present in .config.
However, it seems that if we have a .config that has the errata
enabled, but doesn't contain the _LD_ option, then we end up issuing
the warning before we re-run the Kconfig step.
Eventually, I seem to have ended up with the _LD_ option set. Quite
how, I don't know. When I originally noticed the problem, I had done
a full rebuild. I then re-ran the build several times, and the warning
popped up every time.
Now that I've touched arch/arm64/Kconfig and re-run the build, it
doesn't warn anymore - in fact, while investigating this and stracing,
the option magically set itself and the problem has vanished.
There is definitely weirdness and unpredictability going on with
Kbuild - I can't explain it. Maybe its just become way to complex...
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-02 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 13:13 Regression: commit 987fdfec2410 causes build to incorrectly issue warning Russell King - ARM Linux admin
2021-07-02 14:48 ` Russell King (Oracle) [this message]
2021-07-05 0:31 ` Masahiro Yamada
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=20210702144833.GO22278@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).