mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Anton Protopopov" <aspsk@isovalent.com>,
	"Naresh Kamboju" <naresh.kamboju@linaro.org>
Cc: "open list" <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	"Linux Regressions" <regressions@lists.linux.dev>,
	"Anders Roxell" <anders.roxell@linaro.org>,
	"Dan Carpenter" <dan.carpenter@linaro.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"David Ahern" <dsahern@kernel.org>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Alexander Lobakin" <aleksander.lobakin@intel.com>,
	"Russell King" <rmk+kernel@armlinux.org.uk>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Linus Walleij" <linus.walleij@linaro.org>
Subject: Re: include/linux/build_bug.h:78:41: error: static assertion failed: "struct bpf_fib_lookup size check"
Date: Wed, 03 Apr 2024 10:45:36 +0200	[thread overview]
Message-ID: <347bb21e-98db-4bd5-9ca1-550eac5be9f8@app.fastmail.com> (raw)
In-Reply-To: <CAPyNcWeu+bzyQg9S3wDb43jbfk95Su5XcSRFPzUbS2ofZ=+5Fg@mail.gmail.com>

On Wed, Apr 3, 2024, at 10:10, Anton Protopopov wrote:
> On Wed, Apr 3, 2024 at 10:03 AM Naresh Kamboju
> <naresh.kamboju@linaro.org> wrote:
>>
>> The arm footbridge_defconfig failed with gcc-13 and gcc-8 on Linux next
>> starting from next-20240328..next-20240402.
>>
>> arm:
>>   build:
>>     * gcc-8-footbridge_defconfig - Failed
>>     * gcc-13-footbridge_defconfig - Failed
>>
>> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>>
>> In file included from include/linux/bitfield.h:10,
>>                  from arch/arm/include/asm/ptrace.h:13,
>>                  from arch/arm/include/asm/processor.h:14,
>>                  from include/linux/prefetch.h:15,
>>                  from arch/arm/include/asm/atomic.h:12,
>>                  from include/linux/atomic.h:7,
>>                  from net/core/filter.c:20:
>> include/linux/build_bug.h:78:41: error: static assertion failed:
>> "struct bpf_fib_lookup size check"
>>    78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
>>       |                                         ^~~~~~~~~~~~~~
>
> Thanks, I will take a look today

The problem is CONFIG_AEABI=n, which changes the alignment
of sub-word struct members. I had assumed that AEABI is enabled
by default for everything already, but it looks like footbridge
and a couple of other defconfigs still have it turned off:

$ git grep -l  CONFIG_ARCH_MULTI_V7.is.not arch/arm/configs/* | xargs git grep -L AEABI
arch/arm/configs/assabet_defconfig
arch/arm/configs/collie_defconfig
arch/arm/configs/footbridge_defconfig
arch/arm/configs/h3600_defconfig
arch/arm/configs/jornada720_defconfig
arch/arm/configs/neponset_defconfig
arch/arm/configs/netwinder_defconfig
arch/arm/configs/rpc_defconfig
arch/arm/configs/spear3xx_defconfig
arch/arm/configs/spear6xx_defconfig
arch/arm/configs/spitz_defconfig

Russell still has machines with an OABI toolchain, but I'm not
aware of anyone else relying on it. It does cause other
problems as well, so I already turned it off a long time ago
for my randconfig testing.

We should probably make it the default for everything, except
whichever defconfig Russell uses:

--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -1159,7 +1159,7 @@ config ARM_PATCH_IDIV
 config AEABI
        bool "Use the ARM EABI to compile the kernel" if !CPU_V7 && \
                !CPU_V7M && !CPU_V6 && !CPU_V6K && !CC_IS_CLANG && !COMPILE_TEST
-       default CPU_V7 || CPU_V7M || CPU_V6 || CPU_V6K || CC_IS_CLANG || COMPILE_TEST
+       default y
        help
          This option allows for the kernel to be compiled using the latest
          ARM ABI (aka EABI).  This is only useful if you are using a user

Or we could go one step further and make it 'depends on
EXPERT', short of removing it entirely.

     Arnd

  reply	other threads:[~2024-04-03  8:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03  8:03 Naresh Kamboju
2024-04-03  8:10 ` Anton Protopopov
2024-04-03  8:45   ` Arnd Bergmann [this message]
2024-04-03  9:37     ` Alexander Lobakin
2024-04-03  9:57       ` Anton Protopopov
2024-04-03 10:09         ` Anton Protopopov
2024-04-03 10:12           ` Alexander Lobakin
2024-04-03 11:17           ` Arnd Bergmann

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=347bb21e-98db-4bd5-9ca1-550eac5be9f8@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=aleksander.lobakin@intel.com \
    --cc=anders.roxell@linaro.org \
    --cc=ardb@kernel.org \
    --cc=aspsk@isovalent.com \
    --cc=ast@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=daniel@iogearbox.net \
    --cc=dsahern@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=regressions@lists.linux.dev \
    --cc=rmk+kernel@armlinux.org.uk \
    /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

all inboxes | Powered by JetHome®