[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169238167326.1457886.12849640803727382145.b4-ty@chromium.org>
Date: Fri, 18 Aug 2023 11:01:15 -0700
From: Kees Cook <keescook@...omium.org>
To: Mimi Zohar <zohar@...ux.ibm.com>, Kees Cook <keescook@...omium.org>
Cc: Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
Paul Moore <paul@...l-moore.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Tom Rix <trix@...hat.com>, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev, linux-hardening@...r.kernel.org
Subject: Re: [PATCH] integrity: Annotate struct ima_rule_opt_list with __counted_by
On Thu, 17 Aug 2023 14:03:28 -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 ima_rule_opt_list.
> Additionally, since the element count member must be set before accessing
> the annotated flexible array member, move its initialization earlier.
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] integrity: Annotate struct ima_rule_opt_list with __counted_by
https://git.kernel.org/kees/c/a4b35d4d05b9
Take care,
--
Kees Cook
Powered by blists - more mailing lists