linux-kernel - Re: [tip: x86/asm] x86/asm: Make ASM_CALL_CONSTRAINT conditional on frame pointers

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 for Android: free password hash cracker in your pocket

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

Message-ID: <82FF5D6C-15F5-44FE-8436-CDBB9F35FDD5@zytor.com>
Date: Mon, 03 Mar 2025 18:05:07 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Andrew Cooper <andrew.cooper3@...rix.com>
CC: brgerst@...il.com, jpoimboe@...nel.org, linux-kernel@...r.kernel.org,
        linux-tip-commits@...r.kernel.org, mingo@...nel.org,
        peterz@...radead.org, tip-bot2@...utronix.de,
        torvalds@...ux-foundation.org, x86@...nel.org
Subject: Re: [tip: x86/asm] x86/asm: Make ASM_CALL_CONSTRAINT conditional on frame pointers

On March 3, 2025 4:57:49 PM PST, Andrew Cooper <andrew.cooper3@...rix.com> wrote:
>> One more thing: if we remove ASM_CALL_CONSTRAINTS, we will not be able to use the redzone in future FRED only kernel builds.
>
>That's easy enough to fix with "|| CONFIG_FRED_EXCLUSIVE" in some
>theoretical future when it's a feasible config to use.
>
>~Andrew

Assuming it hasn't bitrotted...