From: Kees Cook <keescook@chromium.org>
To: "David S. Miller" <davem@davemloft.net>,
Kees Cook <keescook@chromium.org>
Cc: sparclinux@vger.kernel.org, Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] sparc: Annotate struct cpuinfo_tree with __counted_by
Date: Fri, 6 Oct 2023 13:25:46 -0700 [thread overview]
Message-ID: <169662394357.2154428.12028362294967452741.b4-ty@chromium.org> (raw)
In-Reply-To: <20230922175159.work.357-kees@kernel.org>
On Fri, 22 Sep 2023 10:52:00 -0700, Kees Cook 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 checking via CONFIG_UBSAN_BOUNDS
> (for array indexing) and CONFIG_FORTIFY_SOURCE (for strcpy/memcpy-family
> functions).
>
> As found with Coccinelle[1], add __counted_by for struct cpuinfo_tree.
>
> [...]
Since this is a trivial change and it's been 2 week without further
discussion, I'll snag this patch.
Applied to for-next/hardening, thanks!
[1/1] sparc: Annotate struct cpuinfo_tree with __counted_by
https://git.kernel.org/kees/c/cfa36f889f23
Take care,
--
Kees Cook
prev parent reply other threads:[~2023-10-06 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 17:52 [PATCH] sparc: Annotate struct cpuinfo_tree with __counted_by Kees Cook
2023-09-23 16:34 ` Gustavo A. R. Silva
2023-10-06 20:25 ` 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=169662394357.2154428.12028362294967452741.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=davem@davemloft.net \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sparclinux@vger.kernel.org \
--cc=trix@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).