linux-kernel - Re: [PATCH 0/2] x86/purgatory: Avoid kexec runtime warning with LLVM 18

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]

Date: Thu, 18 Apr 2024 13:14:35 +0200
From: Borislav Petkov <bp@...en8.de>
To: Nathan Chancellor <nathan@...nel.org>, tglx@...utronix.de, mingo@...hat.com,
 dave.hansen@...ux.intel.com
CC: x86@...nel.org, hpa@...or.com, ndesaulniers@...gle.com, morbo@...gle.com,
 justinstitt@...gle.com, song@...nel.org, ribalda@...omium.org,
 linux-kernel@...r.kernel.org, llvm@...ts.linux.dev, patches@...ts.linux.dev,
 ns <0n-s@...rs.noreply.github.com>
Subject: Re: [PATCH 0/2] x86/purgatory: Avoid kexec runtime warning with LLVM 18

On April 17, 2024 11:53:44 PM GMT+02:00, Nathan Chancellor <nathan@...nel.org> wrote:
>Hi all,
>
>After LLVM commit d8a04398f949 ("Reland [X86] With large code model, put
>functions into .ltext with large section flag (#73037)") [1], which
>landed in the 18.x cycle, there is a runtime warning when loading a
>kernel via kexec due to the presence of two text sections (.text and
>.ltext).

How much of this silliness should we expect now for other parts of the kernel?

Can we turn this off?

Why does llvm enforce .ltext for large code models and why gcc doesn't do that? Why does llvm need to do that, what requirement dictates that?

Thx.

-- 
Sent from a small device: formatting sucks and brevity is inevitable.