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:   Fri, 18 Dec 2020 10:50:22 -0800
From:   Linus Torvalds <>
To:     Kees Cook <>
Cc:     Linux Kernel Mailing List <>,
        Masahiro Yamada <>
Subject: Re: [GIT PULL] gcc-plugins updates for v5.11-rc1

On Wed, Dec 16, 2020 at 12:23 PM Kees Cook <> wrote:
> Hmm. Yeah, that's a bug. I think that's an existing bug, though. I feel
> like I scratched my head on that too. I will see if there is a sensible
> way to have Kbuild "notice" that -- I hope there's an easier way to
> invalidate all object files instead of adding all the plugins as a dep
> to all .o builds. O_o

Side note, there's actually a more annoying issue with the gcc plugin
config code.

Namely that when I get a compiler update, the rest of the Kconfig
system is smart, and rebuilds all my files.

The gcc-plugins code? The code that *really* depends on the compiler
version even more? Yeah, not so much. It ends up instead causing a
build error like

   cc1: error: incompatible gcc/plugin versions
   cc1: error: failed to initialize plugin

because the plugins don't depend on the compiler version.

Again, this is not new, but it's another example of how fragile and
annoying the gcc-plugins code can be.


Powered by blists - more mailing lists