[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250308041950.it.402-kees@kernel.org>
Date: Fri, 7 Mar 2025 20:29:24 -0800
From: Kees Cook <kees@...nel.org>
To: Nathan Chancellor <nathan@...nel.org>
Cc: Kees Cook <kees@...nel.org>,
Nick Desaulniers <nick.desaulniers+lkml@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
Paul Moore <paul@...l-moore.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>,
linux-kernel@...r.kernel.org,
x86@...nel.org,
linux-hardening@...r.kernel.org,
linux-security-module@...r.kernel.org,
llvm@...ts.linux.dev
Subject: [PATCH v2 0/2] hardening: Enable i386 FORTIFY_SOURCE on Clang 16+
Hi,
This drops -ffreestanding for i386 unconditionally for GCC, and on
Clang version 16 and later. FORTIFY_SOURCE depends on the libcall
optimizations made without -ffreestanding on Clang. On GCC, there is no
expected differences. With that done, it's possible to gain Clang
FORTIFY_SOURCE coverage on i386 again, though only for Clang 16+.
-Kees
v1: https://lore.kernel.org/lkml/20250303214929.work.499-kees@kernel.org/
v2: drop -ffreestanding (Nathan)
Kees Cook (2):
x86/build: Remove -ffreestanding on i386 with GCC
hardening: Enable i386 FORTIFY_SOURCE on Clang 16+
arch/x86/Makefile | 2 ++
security/Kconfig.hardening | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
--
2.34.1
Powered by blists - more mailing lists