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] [day] [month] [year] [list]
Message-ID: <20260204082221.GC3016024@noisy.programming.kicks-ass.net>
Date: Wed, 4 Feb 2026 09:22:21 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Nathan Chancellor <nathan@...nel.org>
Cc: kernel test robot <lkp@...el.com>, Thomas Gleixner <tglx@...nel.org>,
	llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>
Subject: Re: kernel/futex/core.c:604:23: error: cannot jump from this asm
 goto statement to one of its possible targets

On Mon, Feb 02, 2026 at 08:56:03PM -0700, Nathan Chancellor wrote:

> This appears to be the same error that necessitated e2ffa15b9baa ("kbuild:
> Disable CC_HAS_ASM_GOTO_OUTPUT on clang < 17") upstream but this is just
> regular 'asm goto', not 'asm goto' with outputs. I had noted during
> review that change might not be sufficient to avoid the error in all
> cases:
> 
>   https://lore.kernel.org/20250916184440.GA1245207@ax162/
> 
> This is not the only recent instance of this error because cleanup
> macros are becoming quite popular so I think it is getting to the point
> where we will need to raise the minimum supported version of LLVM for
> building the kernel to 17.0.1 or newer to ensure that we have this
> fixed. LLVM 22.1.0 should be released in a month or so, so I can look at
> crafting a series for 7.1/7.2 that does this bump.

Works for me, more recent compiler more better and all that ;-)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ