linux-kernel - Re: [GIT PULL] gcc-plugins updates for v5.11-rc1

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]

Message-ID: <CAHk-=wg=2M=4iV5vQMMMGzYiP6Fnx8CpYXomGqKwV1u3-uOq5w@mail.gmail.com>
Date:   Wed, 16 Dec 2020 12:28:14 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Kees Cook <keescook@...omium.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Masahiro Yamada <masahiroy@...nel.org>
Subject: Re: [GIT PULL] gcc-plugins updates for v5.11-rc1

On Wed, Dec 16, 2020 at 12:23 PM Kees Cook <keescook@...omium.org> 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

We already have some support for checking the compiler version. I
wonder if the plugins could add themselves to the version name in
there somehow..

But I don't think it's a big deal, and I won't worry about it. I do
hope we can deprecate the plugins some day, it has always made me very
nervous to have random code at that level.

             Linus