linux-kernel - Re: [PATCH] gcc-plugins: use KERNELVERSION for plugin version

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] [day] [month] [year] [list]

Message-Id: <165340601337.1531311.10949376876252513636.b4-ty@chromium.org>
Date:   Tue, 24 May 2022 08:26:55 -0700
From:   Kees Cook <keescook@...omium.org>
To:     linux@...ck-us.net, masahiroy@...nel.org,
        linux-hardening@...r.kernel.org
Cc:     Kees Cook <keescook@...omium.org>, lkp@...el.com,
        linux-kbuild@...r.kernel.org, ndesaulniers@...gle.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] gcc-plugins: use KERNELVERSION for plugin version

On Tue, 24 May 2022 22:55:41 +0900, Masahiro Yamada wrote:
> Commit 61f60bac8c05 ("gcc-plugins: Change all version strings match
> kernel") broke parallel builds.
> 
> Instead of adding the dependency between GCC plugins and utsrelease.h,
> let's use KERNELVERSION, which does not require any build artifact.
> 
> Another reason why I want to avoid utsrelease.h is because it depends
> on CONFIG_LOCALVERSION(_AUTO) and localversion* files.
> 
> [...]

Ah, perfect; I appreciate the better solution! Applied to
for-next/hardening, thanks!

[1/1] gcc-plugins: use KERNELVERSION for plugin version
      https://git.kernel.org/kees/c/d37aa2efc89b

-- 
Kees Cook