Linux-Hardening mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Alexey Dobriyan <adobriyan@gmail.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Dmitry Antipov <dmantipov@yandex.ru>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Justin Stitt <justinstitt@google.com>,
	Sven Eckelmann <sven@narfation.org>,
	Erick Archer <erick.archer@outlook.com>
Cc: Kees Cook <keescook@chromium.org>,
	Alexander Lobakin <aleksander.lobakin@intel.com>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] uapi: stddef.h: Provide UAPI macros for __counted_by_{le, be}
Date: Wed,  8 May 2024 00:43:04 -0700	[thread overview]
Message-ID: <171515418204.39234.18138383965654677988.b4-ty@chromium.org> (raw)
In-Reply-To: <AS8PR02MB72372E45071E8821C07236F78BE42@AS8PR02MB7237.eurprd02.prod.outlook.com>

On Tue, 07 May 2024 19:33:18 +0200, Erick Archer wrote:
> This commit can be considered an addition to commit ca7e324e8ad3
> ("compiler_types: add Endianness-dependent __counted_by_{le,be}") [1].
> 
> In the commit referenced above the __counted_by_{le,be}() attributes
> were defined based on platform's endianness with the goal to that the
> structures contain flexible arrays at the end, and the counter for,
> can be annotated with these attributes.
> 
> [...]

Applied to for-next/hardening, thanks!

[1/1] uapi: stddef.h: Provide UAPI macros for __counted_by_{le, be}
      https://git.kernel.org/kees/c/6d305cbef1aa

Take care,

-- 
Kees Cook


      reply	other threads:[~2024-05-08  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07 17:33 [PATCH v2] uapi: stddef.h: Provide UAPI macros for __counted_by_{le, be} Erick Archer
2024-05-08  7:43 ` 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=171515418204.39234.18138383965654677988.b4-ty@chromium.org \
    --to=keescook@chromium.org \
    --cc=adobriyan@gmail.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=dmantipov@yandex.ru \
    --cc=erick.archer@outlook.com \
    --cc=gustavoars@kernel.org \
    --cc=justinstitt@google.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=sven@narfation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).