linux-kernel - Re: [GIT PULL] Kbuild updates for 4.18 (2nd round)

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: <CA+55aFz7KGMcvABxJfYs719ySyt2JouDX9t0SAV4Qu9yY9tfPA@mail.gmail.com>
Date:   Wed, 13 Jun 2018 10:49:16 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Kbuild updates for 4.18 (2nd round)

On Wed, Jun 13, 2018 at 10:29 AM Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:
>
> I cannot come up with a name better than CC_STACKPROTECTOR_STRONG.

How about just calling it STACKPROTETOR_STRONG and leaving it at that?

Make the "CC_HAVE_xyz" model for compiler feature tests, but when
actually picking an actual option, it's not really about the compiler
any more, except in the sense that it depends on it.

I guess we could leave the CC_STACKPROTECTOR option as-is, just
because it apparently has a lot of small uses in actual code too, but
there is absolutely nothing that uses CONFIG_CC_STACKPROTECTOR_STRONG
outside of the actual compiler option choice (and config files)

                Linus