From: Justin Stitt <justinstitt@google.com>
To: Nathan Chancellor <nathan@kernel.org>,
Kees Cook <kees@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>
Cc: linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, linux-kselftest@vger.kernel.org,
Justin Stitt <justinstitt@google.com>
Subject: [PATCH] MAINTAINERS: Add stackinit KUnit test to HARDENING
Date: Fri, 2 Oct 2026 12:27:17 -0700 [thread overview]
Message-ID: <20261002-maintainers-stackinit-v1-1-27112a221527@google.com> (raw)
From: Justin Stitt <justinstitt@google.com>
Noticed while preparing a patch to lib/tests/stackinit_kunit.c: the file
is not listed in MAINTAINERS, so get_maintainer.pl does not suggest Kees
or linux-hardening for changes to it, only the catch-all list.
before:
$ ./scripts/get_maintainer.pl -f lib/tests/stackinit_kunit.c
linux-kernel@vger.kernel.org (open list)
after:
$ ./scripts/get_maintainer.pl -f lib/tests/stackinit_kunit.c
Kees Cook <kees@kernel.org> (maintainer:KERNEL HARDENING
"Gustavo A. R. Silva" <gustavoars@kernel.org> (reviewer:KERNEL HARDENING
linux-hardening@vger.kernel.org (open list:KERNEL HARDENING
linux-kernel@vger.kernel.org (open list)
Signed-off-by: Justin Stitt <justinstitt@google.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4f72b4ac27ee..019f443af051 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14164,6 +14164,7 @@ F: include/linux/ucopysize.h
F: kernel/configs/hardening.config
F: kernel/kstack_erase.c
F: lib/tests/randstruct_kunit.c
+F: lib/tests/stackinit_kunit.c
F: lib/tests/usercopy_kunit.c
F: mm/usercopy.c
F: scripts/Makefile.kstack_erase
---
base-commit: 5e0f8396d4805a3e7f753fa58c8c55f1f3cc2160
change-id: 20261002-maintainers-stackinit-230afe234e5a
Best regards,
--
Justin Stitt <justinstitt@google.com>
next reply other threads:[~2026-10-02 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 19:27 Justin Stitt [this message]
2026-10-02 20:42 ` Nick Desaulniers
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=20261002-maintainers-stackinit-v1-1-27112a221527@google.com \
--to=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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
all inboxes | Powered by JetHome®