linux-kernel - Re: Build breakage caused by the use of UDB

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: <20251218103853.GS3911114@noisy.programming.kicks-ass.net>
Date: Thu, 18 Dec 2025 11:38:53 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Uros Bizjak <ubizjak@...il.com>
Cc: Jean Delvare <jdelvare@...e.de>, LKML <linux-kernel@...r.kernel.org>,
	Josh Poimboeuf <jpoimboe@...hat.com>, ardb@...nel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>, x86@...nel.org
Subject: Re: Build breakage caused by the use of UDB

On Thu, Dec 18, 2025 at 11:26:13AM +0100, Uros Bizjak wrote:

> I see... OTOH, a trivial solution would be to just use "ud2" mnemonic,
> as proposed in [1].
> 
> [1] https://lore.kernel.org/lkml/20250909100038.1709394-1-ubizjak@gmail.com/

Yes, there is that. I suppose I worry about all the other _ASM_BYTES
users, but since they don't actually show miscompilation, perhaps I
should not worry.

Let me do a build with just using ud2 instead.