linux-kernel - Re: [PATCH 01/15] ARM: use CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdYmCzYT6s3XaQURLW9ak1xvzuKPpm_LB5GM+AzNUHtv7g@mail.gmail.com>
Date: Wed, 4 Dec 2024 14:54:23 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Arnd Bergmann <arnd@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
	Arnd Bergmann <arnd@...db.de>, Aaro Koskinen <aaro.koskinen@....fi>, Andrew Lunn <andrew@...n.ch>, 
	Ard Biesheuvel <ardb@...nel.org>, Daniel Mack <daniel@...que.org>, 
	Gregory Clement <gregory.clement@...tlin.com>, Haojian Zhuang <haojian.zhuang@...il.com>, 
	"Jeremy J. Peper" <jeremy@...emypeper.com>, Kristoffer Ericson <kristoffer.ericson@...il.com>, 
	Krzysztof Kozlowski <krzk@...nel.org>, Mark Brown <broonie@...nel.org>, 
	Ralph Siemsen <ralph.siemsen@...aro.org>, Robert Jarzmik <robert.jarzmik@...e.fr>, 
	Russell King <linux@...linux.org.uk>, 
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>, Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCH 01/15] ARM: use CONFIG_AEABI by default everywhere

On Wed, Dec 4, 2024 at 11:29 AM Arnd Bergmann <arnd@...nel.org> wrote:

> From: Arnd Bergmann <arnd@...db.de>
>
> On ARMv4 and ARMv5, the default is still to build for OABI, with
> CONFIG_AEABI disabled, even though distros and toolchains no longer
> support OABI as a target.
>
> Change the default to EABI for all architecture levels and change
> the defconfig entries as follows:
>
>  - All machines that used to explicitly enable EABI can drop that line now
>  - Machines that are likely to actually use old distros and had NWFPE
>    enabled in combination with OABI (rpc, footrbridge, netwinder,
>    assabet, neponset) explicitly turn it on now.
>  - Machines that already had both EABI and NWFPE disabled in defconfig
>    (at91_dt, collie, ep93xx, gemini, h3600, imx_v4_v5, integrator, jornada,
>    moxart, multi_v4t, omap1) were likely not usable with either OABI or
>    EABI and now use EABI instead implicitly, making it more likely that
>    they could work.
>
> Signed-off-by: Arnd Bergmann <arnd@...db.de>

For these:

>  arch/arm/configs/gemini_defconfig       |  1 -
>  arch/arm/configs/integrator_defconfig   |  1 -
>  arch/arm/configs/ixp4xx_defconfig       |  1 -
>  arch/arm/configs/netwinder_defconfig    |  1 +
>  arch/arm/configs/nhk8815_defconfig      |  1 -
>  arch/arm/configs/versatile_defconfig    |  1 -

Acked-by: Linus Walleij <linus.walleij@...aro.org>

I only ever use these platforms with AEABI, and a corresponding
userspace.

My userspace for the Faraday FA526 uses the OpenWrt-resident
GCC --fix-v4bx hack:
https://github.com/openwrt/openwrt/blob/main/toolchain/gcc/patches-14.x/840-armv4_pass_fix-v4bx_to_ld.patch
(maybe this is a bit sloppy but it works for us)

Maybe LLVM CLANG can build an ARMv4 userspace without this
hack? I haven't looked closer.

Yours,
Linus Walleij