From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Clemens Ladisch <clemens@ladisch.de>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] hpet: Replace one-element array with flexible-array member
Date: Thu, 17 Nov 2022 21:54:04 -0600 [thread overview]
Message-ID: <Y3cB3MqiM+KFJHNm@work> (raw)
In-Reply-To: <20221118034250.never.999-kees@kernel.org>
On Thu, Nov 17, 2022 at 07:42:55PM -0800, Kees Cook wrote:
> One-element arrays are deprecated[1] and are being replaced with
> flexible array members in support of the ongoing efforts to tighten the
> FORTIFY_SOURCE routines on memcpy(), correctly instrument array indexing
> with UBSAN_BOUNDS, and to globally enable -fstrict-flex-arrays=3.
>
> Replace one-element array with flexible-array member in struct hpet.
>
> This results in no differences in binary output. The use of struct hpet
> is never used with sizeof() and accesses via hpet_timers array are
> already done after explicit bounds checking.
>
> [1] https://github.com/KSPP/linux/issues/79
>
> Cc: Clemens Ladisch <clemens@ladisch.de>
> Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>
> Signed-off-by: Kees Cook <keescook@chromium.org>
Such a sneaky 1-element... ~.~
Reviewed-by: Gustavo A. R. Silva <gustavoars@kernel.org>
Thanks!
--
Gustavo
> ---
> include/linux/hpet.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/hpet.h b/include/linux/hpet.h
> index 8604564b985d..21e69eaf7a36 100644
> --- a/include/linux/hpet.h
> +++ b/include/linux/hpet.h
> @@ -30,7 +30,7 @@ struct hpet {
> unsigned long _hpet_compare;
> } _u1;
> u64 hpet_fsb[2]; /* FSB route */
> - } hpet_timers[1];
> + } hpet_timers[];
> };
>
> #define hpet_mc _u0._hpet_mc
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-11-18 3:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 3:42 [PATCH] hpet: Replace one-element array with flexible-array member Kees Cook
2022-11-18 3:54 ` Gustavo A. R. Silva [this message]
2022-11-18 4:23 ` Kees Cook
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=Y3cB3MqiM+KFJHNm@work \
--to=gustavoars@kernel.org \
--cc=clemens@ladisch.de \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.