From: Eric Biggers <ebiggers@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: hardening: Add __counted_by regex
Date: Mon, 25 Sep 2023 21:57:21 -0700 [thread overview]
Message-ID: <20230926045721.GA3118@sol.localdomain> (raw)
In-Reply-To: <20230925172037.work.853-kees@kernel.org>
Hi Kees,
On Mon, Sep 25, 2023 at 10:20:41AM -0700, Kees Cook wrote:
> Since __counted_by annotations may also require that code be changed to
> get initialization ordering correct, let's get an extra group of eyes on
> code that is working on these annotations.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 737dcc7a2155..741285b8246e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11405,6 +11405,7 @@ F: kernel/configs/hardening.config
> F: mm/usercopy.c
> K: \b(add|choose)_random_kstack_offset\b
> K: \b__check_(object_size|heap_object)\b
> +K: \b__counted_by\b
>
Are you sure you want to volunteer to maintain every file that contains
"__counted_by"? That's what "K" does; get_maintainer.pl will list you (and
linux-hardening@vger.kernel.org) for every such file.
Other users of "K" have been surprised by this behavior. It seems that most
people expect it to only apply to patches, not to files. Given that you're
interested in using this functionality, have you considered updating
checkpatch.pl to handle it in the way that you probably expect that it works?
- Eric
next prev parent reply other threads:[~2023-09-26 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 17:20 [PATCH] MAINTAINERS: hardening: Add __counted_by regex Kees Cook
2023-09-26 4:57 ` Eric Biggers [this message]
2023-09-26 8:35 ` Justin Stitt
2023-09-26 8:41 ` Justin Stitt
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=20230926045721.GA3118@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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