[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172291833913.3365241.1557417143670946391.b4-ty@kernel.org>
Date: Mon, 5 Aug 2024 21:25:41 -0700
From: Kees Cook <kees@...nel.org>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Kees Cook <kees@...nel.org>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
linux-hardening@...r.kernel.org,
llvm@...ts.linux.dev
Subject: Re: [PATCH v2 0/3] fortify: fix various issues in test_fortify Makefile
On Sun, 28 Jul 2024 00:02:35 +0900, Masahiro Yamada wrote:
> This version fixes new warnings for GCC <= 7, which were reported
> by 0 day bot.
>
> I changed the patch order, as 3/3 is the most controvertial.
> I am confident with 1/3 and 2/3.
> 3/3 drops the test coverage for GCC <= 7.
>
> [...]
Applied to for-next/hardening, thanks!
[1/3] fortify: refactor test_fortify Makefile to fix some build problems
https://git.kernel.org/kees/c/61b317f70aa7
[2/3] fortify: move test_fortify.sh to lib/test_fortify/
https://git.kernel.org/kees/c/728dc04bc4e3
[3/3] fortify: use if_changed_dep to record header dependency in *.cmd files
https://git.kernel.org/kees/c/634a52a98f04
Take care,
--
Kees Cook
Powered by blists - more mailing lists