From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Kees Cook <keescook@chromium.org>, Pavel Machek <pavel@ucw.cz>
Cc: "Lee Jones" <lee@kernel.org>,
"Bjorn Andersson" <quic_bjorande@quicinc.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Douglas Anderson" <dianders@chromium.org>,
"Anjelique Melendez" <quic_amelende@quicinc.com>,
linux-leds@vger.kernel.org,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Tom Rix" <trix@redhat.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Luca Weiss" <luca@z3ntu.xyz>, "Lu Hongfei" <luhongfei@vivo.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] leds: qcom-lpg: Annotate struct lpg_led with __counted_by
Date: Fri, 15 Sep 2023 14:47:56 -0600 [thread overview]
Message-ID: <3b98d3af-02ef-8929-1e6b-7287f470df2a@embeddedor.com> (raw)
In-Reply-To: <20230915201059.never.086-kees@kernel.org>
On 9/15/23 14:11, 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 lpg_led.
>
> [1] https://github.com/kees/kernel-tools/blob/trunk/coccinelle/examples/counted_by.cocci
>
> Cc: Pavel Machek <pavel@ucw.cz>
> Cc: Lee Jones <lee@kernel.org>
> Cc: Bjorn Andersson <quic_bjorande@quicinc.com>
> Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
> Cc: Douglas Anderson <dianders@chromium.org>
> Cc: Anjelique Melendez <quic_amelende@quicinc.com>
> Cc: linux-leds@vger.kernel.org
> Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-by: Gustavo A. R. Silva <gustavoars@kernel.org>
Thanks
--
Gustavo
> ---
> drivers/leds/rgb/leds-qcom-lpg.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/leds/rgb/leds-qcom-lpg.c b/drivers/leds/rgb/leds-qcom-lpg.c
> index df469aaa7e6e..7d93e02a030a 100644
> --- a/drivers/leds/rgb/leds-qcom-lpg.c
> +++ b/drivers/leds/rgb/leds-qcom-lpg.c
> @@ -173,7 +173,7 @@ struct lpg_led {
> struct led_classdev_mc mcdev;
>
> unsigned int num_channels;
> - struct lpg_channel *channels[];
> + struct lpg_channel *channels[] __counted_by(num_channels);
> };
>
> /**
next prev parent reply other threads:[~2023-09-15 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 20:11 [PATCH] leds: qcom-lpg: Annotate struct lpg_led with __counted_by Kees Cook
2023-09-15 20:47 ` Gustavo A. R. Silva [this message]
2023-09-20 13:42 ` (subset) " Lee Jones
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=3b98d3af-02ef-8929-1e6b-7287f470df2a@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=keescook@chromium.org \
--cc=lee@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luca@z3ntu.xyz \
--cc=luhongfei@vivo.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=neil.armstrong@linaro.org \
--cc=pavel@ucw.cz \
--cc=quic_amelende@quicinc.com \
--cc=quic_bjorande@quicinc.com \
--cc=trix@redhat.com \
--cc=u.kleine-koenig@pengutronix.de \
/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