The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thorsten Blum <thorsten.blum@linux.dev>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Kees Cook <kees@kernel.org>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Tim Bird <tim.bird@sony.com>,
	keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH net-next v3 2/2] KEYS: annotate struct user_key_payload with __counted_by
Date: Sun, 10 May 2026 12:47:24 +0200	[thread overview]
Message-ID: <agBiPEJZhWHydwuz@linux.dev> (raw)
In-Reply-To: <af8ZUXn4uStU_vs5@kernel.org>

On Sat, May 09, 2026 at 02:24:01PM +0300, Jarkko Sakkinen wrote:
> On Mon, Apr 27, 2026 at 01:44:24PM +0200, Thorsten Blum wrote:
> > Add the __counted_by() compiler attribute to the flexible array member
> > 'data' to improve bounds checking via CONFIG_UBSAN_BOUNDS and
> > CONFIG_FORTIFY_SOURCE.
> > 
> > Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> 
> This is again a crippled commit message.
> 
> I.e. this requires either knowing, remembering and/or cross-referencing
> "bunch of" unrelated to keyring.

I kept the commit message short because it follows the same pattern as
many other __counted_by() patches that have been accepted across several
subsystems.

I'm not sure which part of the message you want expanded. Could you be
more specific?

Thanks,
Thorsten

  reply	other threads:[~2026-05-10 10:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260427114422.313356-3-thorsten.blum@linux.dev>
2026-05-08 21:21 ` [PATCH net-next v3 1/2] keys, dns: drop unused upayload->data NUL terminator Jarkko Sakkinen
2026-05-08 22:22   ` Thorsten Blum
     [not found] ` <20260427114422.313356-4-thorsten.blum@linux.dev>
2026-05-09 11:24   ` [PATCH net-next v3 2/2] KEYS: annotate struct user_key_payload with __counted_by Jarkko Sakkinen
2026-05-10 10:47     ` Thorsten Blum [this message]
2026-05-10 14:12       ` Jarkko Sakkinen
2026-05-10 14:14         ` Jarkko Sakkinen

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=agBiPEJZhWHydwuz@linux.dev \
    --to=thorsten.blum@linux.dev \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=gustavoars@kernel.org \
    --cc=horms@kernel.org \
    --cc=jarkko@kernel.org \
    --cc=kees@kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tim.bird@sony.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