linux-kernel - Re: [tip:master 19/19] include/linux/irq-entry-common.h:201:2: error: unexpected token

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: <aGUtCveV8Ev17_FS@J2N7QTR9R3.cambridge.arm.com>
Date: Wed, 2 Jul 2025 13:58:50 +0100
From: Mark Rutland <mark.rutland@....com>
To: Borislav Petkov <bp@...en8.de>
Cc: kernel test robot <lkp@...el.com>, Thomas Gleixner <tglx@...utronix.de>,
	llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
	linux-kernel@...r.kernel.org, x86@...nel.org,
	Linus Walleij <linus.walleij@...aro.org>,
	Jinjie Ruan <ruanjinjie@...wei.com>
Subject: Re: [tip:master 19/19] include/linux/irq-entry-common.h:201:2:
 error: unexpected token

Hi Boris,

[ adding Linux and Jinjie, since this is almost certainly due to the
  irqentry split ]

On Wed, Jul 02, 2025 at 02:32:40PM +0200, Borislav Petkov wrote:
> On Wed, Jul 02, 2025 at 05:56:06AM +0800, kernel test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
> > head:   104f02a7798f7e8aba25545f9d485035532260b2
> > commit: 104f02a7798f7e8aba25545f9d485035532260b2 [19/19] Merge core/entry into tip/master
> > config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20250702/202507020528.N0LtekXt-lkp@intel.com/config)
> > compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250702/202507020528.N0LtekXt-lkp@intel.com/reproduce)
> 
> I'm trying to follow your reproducer and installed binutils-s390x-linux-gnu.
> 
> However: 
> 
> make CC=clang HOSTCC=clang W=1 ARCH=s390 arch/s390/ 
>   SYNC    include/config/auto.conf.cmd
>   CALL    scripts/checksyscalls.sh
>   VDSO    arch/s390/kernel/vdso64/vdso64.so.dbg
> ld: unrecognised emulation mode: elf64_s390
> Supported emulations: elf_x86_64 elf32_x86_64 elf_i386 elf_iamcu i386pep i386pe
> make[2]: *** [arch/s390/kernel/vdso64/Makefile:53: arch/s390/kernel/vdso64/vdso64.so.dbg] Error 1
> make[1]: *** [arch/s390/Makefile:150: vdso_prepare] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
> 
> My linker can't do s390. So I need something else which your system has.

IIUC you can build with `LLVM=1` rather than `CC=clang` to force the use of
LLD (which should support s390 even if you don't have a GNU LD that does).

I have script to use the kernel.org GCC/LLVM builds from:

  https://www.kernel.org/pub/tools/crosstool/
  https://cdn.kernel.org/pub/tools/llvm/

... and I can reproduce this with:

  [mark@...rids:~/src/linux]% git clean -qfdx
  [mark@...rids:~/src/linux]% usekorg-llvm 18.1.6 make LLVM=1 ARCH=s390 -s allmodconfig
  [mark@...rids:~/src/linux]% usekorg-llvm 18.1.6 make LLVM=1 ARCH=s390 -s  

... where that last step blows up with:

| init/main.c:972:6: error: unexpected token
|   972 |         if (WARN(!irqs_disabled(),
|       |             ^

... plus a whole bucnh of other gunk.

I'll take a look, and hopefully Linus and Jinie can too.

Mark.