From: Eric Biggers <ebiggers@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Kees Cook <keescook@chromium.org>,
linux-hardening@vger.kernel.org, llvm@lists.linux.dev,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Bill Wendling <morbo@google.com>
Subject: Re: [PATCH] randstruct: temporarily disable clang support
Date: Tue, 7 Feb 2023 22:55:00 -0800 [thread overview]
Message-ID: <Y+NHRHsp9u4ooOdf@sol.localdomain> (raw)
In-Reply-To: <CAKwvOdm8F_VcdegPGw3vPu+-H1Gyh0rqQWpf=+Yh9YAowVuWSA@mail.gmail.com>
On Tue, Feb 07, 2023 at 10:01:21AM -0800, Nick Desaulniers wrote:
> On Mon, Feb 6, 2023 at 3:41 PM Fangrui Song <maskray@google.com> wrote:
> >
> > On Sat, Feb 4, 2023 at 11:06 AM Kees Cook <keescook@chromium.org> wrote:
> > >
> > > On Fri, Feb 03, 2023 at 11:42:01AM -0800, Eric Biggers wrote:
> > > > From: Eric Biggers <ebiggers@google.com>
> > > >
> > > > Randstruct with clang is currently unsafe to use in any clang release
> > > > that supports it, due to a clang bug that is causing miscompilations:
> > > > "-frandomize-layout-seed inconsistently randomizes all-function-pointers
> > > > structs" (https://github.com/llvm/llvm-project/issues/60349). Disable
> > > > it temporarily until the bug is fixed and the fix is released in a clang
> > > > version that can be checked for.
> > > >
> > > > Fixes: 035f7f87b729 ("randstruct: Enable Clang support")
> > > > Cc: stable@vger.kernel.org
> > > > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > > > ---
> > > > security/Kconfig.hardening | 3 ++-
> > > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/security/Kconfig.hardening b/security/Kconfig.hardening
> > > > index 53baa95cb644..aad16187148c 100644
> > > > --- a/security/Kconfig.hardening
> > > > +++ b/security/Kconfig.hardening
> > > > @@ -280,7 +280,8 @@ config ZERO_CALL_USED_REGS
> > > > endmenu
> > > >
> > > > config CC_HAS_RANDSTRUCT
> > > > - def_bool $(cc-option,-frandomize-layout-seed-file=/dev/null)
> > > > + # Temporarily disabled due to https://github.com/llvm/llvm-project/issues/60349
> > > > + def_bool n
> > > >
> > > > choice
> > > > prompt "Randomize layout of sensitive kernel structures"
> > > >
> > > > base-commit: 7b753a909f426f2789d9db6f357c3d59180a9354
> > > > --
> > > > 2.39.1
> > >
> > > This should be fixed with greater precision -- i.e. this is nearly fixed
> > > in Clang now, and is likely to be backported. So I think we'll need
> > > versioned checks here.
> > >
> > > --
> > > Kees Cook
> > >
> >
> > Bill has requested cherry-pick the llvm-project fix into the
> > release/16.x branch [1].
> > https://github.com/llvm/llvm-project-release-prs/pull/276
> > It may take one day to land.
> >
> > [1]: https://github.com/llvm/llvm-project/tree/release/16.x
> >
> > --
> > 宋方睿
> >
>
> All landed; the version check should be for 16+. (And the link to the
> issue report would be nice to retain).
Thanks! Done in "[PATCH] randstruct: disable Clang 15 support"
(https://lore.kernel.org/linux-hardening/20230208065133.220589-1-ebiggers@kernel.org).
- Eric
prev parent reply other threads:[~2023-02-08 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 19:42 [PATCH] randstruct: temporarily disable clang support Eric Biggers
2023-02-04 19:06 ` Kees Cook
2023-02-06 23:41 ` Fangrui Song
2023-02-07 18:01 ` Nick Desaulniers
2023-02-08 6:55 ` Eric Biggers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+NHRHsp9u4ooOdf@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=ndesaulniers@google.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox