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  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:   Tue, 21 Aug 2018 09:32:24 -0700
From:   Nick Desaulniers <>
Cc:     Masahiro Yamada <>,
        Kees Cook <>,
        Linus Torvalds <>,, Jonathan Corbet <>,
        Arnd Bergmann <>,,
        LKML <>,
        Thomas Gleixner <>,
        Will Deacon <>,
        Geert Uytterhoeven <>,
        Ingo Molnar <>,
        Andrew Morton <>
Subject: Re: [PATCH] compiler-gcc: get back Clang build

On Tue, Aug 21, 2018 at 5:38 AM Dominique Martinet
<> wrote:
> Nick Desaulniers Aug. 21, 2018, 8:09 a.m. UTC:
> > Thanks for noticing, and sending this patch.  I'm happy to see others
> > testing with Clang.  I noticed this too near the end of the day
> >
> FWIW libbcc so many BPF users also use clang, so this has more impact
> than just testing to build linux with clang (not that this would be any
> reason to delay fixing either way)
> I would tend to agree havin a compiler-common + make clang/intel not
> include compiler-gcc would probably be best in the long run but we might
> want a quick fix for 4.19 meanwhile..

That's fair. SOP here is quick (full) revert, then come up with a
better fix.  And I do prefer Masahiro's partial revert to a full
revert of Joe's patch.  That will give us more time to develop the
proper fix rather than rush.  I'll try to see how we can more properly
split the compiler specific headers.

Tested with gcc-7 and clang-8.

Tested-by: Nick Desaulniers <>
~Nick Desaulniers

Powered by blists - more mailing lists