All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Kees Cook <kees@kernel.org>
Cc: linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] overflow: Clarify expectations for getting DEFINE_FLEX variable sizes
Date: Wed, 16 Apr 2025 12:29:47 -0700	[thread overview]
Message-ID: <174483177863.740549.2239617505557790214.b4-ty@kernel.org> (raw)
In-Reply-To: <20250416172911.work.854-kees@kernel.org>

On Wed, 16 Apr 2025 10:29:15 -0700, Kees Cook wrote:
> Mention the use of __member_size() for DEFINE_FLEX variables as a hint
> for getting at the compile-time size of the resulting flexible array
> member.
> 
> 

Applied to for-next/hardening, thanks!

[1/1] overflow: Clarify expectations for getting DEFINE_FLEX variable sizes
      https://git.kernel.org/kees/c/2122b4571745

Take care,

-- 
Kees Cook


      parent reply	other threads:[~2025-04-16 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 17:29 [PATCH] overflow: Clarify expectations for getting DEFINE_FLEX variable sizes Kees Cook
2025-04-16 17:37 ` Gustavo A. R. Silva
2025-04-16 19:29 ` Kees Cook [this message]

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=174483177863.740549.2239617505557790214.b4-ty@kernel.org \
    --to=kees@kernel.org \
    --cc=gustavoars@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.