From: Kees Cook <keescook@chromium.org>
To: Russell King <linux@armlinux.org.uk>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] atags_proc: Add __counted_by for struct buffer and use struct_size()
Date: Sat, 2 Dec 2023 12:32:23 -0800 [thread overview]
Message-ID: <170154914064.179444.11376018592445133931.b4-ty@chromium.org> (raw)
In-Reply-To: <ZSVHurzo/4aFQcT3@work>
On Tue, 10 Oct 2023 06:46:50 -0600, Gustavo A. R. Silva wrote:
> Prepare for the coming implementation by GCC and Clang of the __counted_by
> attribute. Flexible array members annotated with __counted_by can have
> their accesses bounds-checked at run-time via CONFIG_UBSAN_BOUNDS (for
> array indexing) and CONFIG_FORTIFY_SOURCE (for strcpy/memcpy-family
> functions).
>
> While there, use struct_size() helper, instead of the open-coded
> version, to calculate the size for the allocation of the whole
> flexible structure, including of course, the flexible-array member.
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] atags_proc: Add __counted_by for struct buffer and use struct_size()
https://git.kernel.org/kees/c/ac7110d883ff
Take care,
--
Kees Cook
prev parent reply other threads:[~2023-12-02 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 12:46 [PATCH][next] atags_proc: Add __counted_by for struct buffer and use struct_size() Gustavo A. R. Silva
2023-10-10 17:58 ` Justin Stitt
2023-10-10 23:09 ` Kees Cook
2023-12-02 20:32 ` 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=170154914064.179444.11376018592445133931.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=gustavoars@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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 NNTP newsgroup(s).