[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240727150302.1823750-1-masahiroy@kernel.org>
Date: Sun, 28 Jul 2024 00:02:35 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Kees Cook <kees@...nel.org>
Cc: linux-kernel@...r.kernel.org,
Masahiro Yamada <masahiroy@...nel.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: [PATCH v2 0/3] fortify: fix various issues in test_fortify Makefile
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.
Masahiro Yamada (3):
fortify: refactor test_fortify Makefile to fix some build problems
fortify: move test_fortify.sh to lib/test_fortify/
fortify: use if_changed_dep to record header dependency in *.cmd files
MAINTAINERS | 1 -
lib/.gitignore | 2 -
lib/Makefile | 38 +------------------
lib/test_fortify/.gitignore | 2 +
lib/test_fortify/Makefile | 28 ++++++++++++++
{scripts => lib/test_fortify}/test_fortify.sh | 0
6 files changed, 31 insertions(+), 40 deletions(-)
create mode 100644 lib/test_fortify/.gitignore
create mode 100644 lib/test_fortify/Makefile
rename {scripts => lib/test_fortify}/test_fortify.sh (100%)
--
2.43.0
Powered by blists - more mailing lists