From: Lukas Bulwahn <lbulwahn@redhat.com>
To: Kees Cook <kees@kernel.org>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
linux-hardening@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: [PATCH] MAINTAINERS: adjust entries in FORTIFY_SOURCE and KERNEL HARDENING
Date: Mon, 17 Feb 2025 11:06:43 +0100 [thread overview]
Message-ID: <20250217100643.20182-1-lukas.bulwahn@redhat.com> (raw)
From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
Commit db6fe4d61ece ("lib: Move KUnit tests into tests/ subdirectory") adds
a file entry to the non-existing file scripts/test_fortify.sh. Probably,
this entry intends to refer to ./lib/test_fortify/test_fortify.sh, though.
As that file is already covered by the entry lib/test_fortify/*, there is
no need for a separate file entry. So, drop the unnecessary file entry to
the test_fortify script.
Further, this commit misses to adjust the entry referring to
lib/usercopy_kunit.c, which is moved to lib/tests. So, also adjust that
file entry.
Fixes: db6fe4d61ece ("lib: Move KUnit tests into tests/ subdirectory")
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
---
MAINTAINERS | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 53cf3cbf33c9..15632a34b740 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9070,7 +9070,6 @@ F: include/linux/fortify-string.h
F: lib/test_fortify/*
F: lib/tests/fortify_kunit.c
F: lib/tests/memcpy_kunit.c
-F: scripts/test_fortify.sh
K: \bunsafe_memcpy\b
K: \b__NO_FORTIFY\b
@@ -12613,7 +12612,7 @@ F: arch/*/configs/hardening.config
F: include/linux/overflow.h
F: include/linux/randomize_kstack.h
F: kernel/configs/hardening.config
-F: lib/usercopy_kunit.c
+F: lib/tests/usercopy_kunit.c
F: mm/usercopy.c
F: security/Kconfig.hardening
K: \b(add|choose)_random_kstack_offset\b
--
2.48.1
next reply other threads:[~2025-02-17 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 10:06 Lukas Bulwahn [this message]
2025-02-22 0:52 ` [PATCH] MAINTAINERS: adjust entries in FORTIFY_SOURCE and KERNEL HARDENING Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250217100643.20182-1-lukas.bulwahn@redhat.com \
--to=lbulwahn@redhat.com \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox