From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Kees Cook <keescook@chromium.org>, KP Singh <kpsingh@kernel.org>
Cc: linux-hardening@vger.kernel.org,
kernel test robot <lkp@intel.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gcc-plugins: randstruct: Only warn about true flexible arrays
Date: Mon, 6 Nov 2023 09:53:36 -0600 [thread overview]
Message-ID: <66a8cc44-15fb-457d-bea6-3a67a6a62630@embeddedor.com> (raw)
In-Reply-To: <20231104204334.work.160-kees@kernel.org>
On 11/4/23 14:43, Kees Cook wrote:
> The randstruct GCC plugin tried to discover "fake" flexible arrays
> to issue warnings about them in randomized structs. In the future
> LSM overhead reduction series, it would be legal to have a randomized
> struct with a 1-element array, and this should _not_ be treated as a
> flexible array, especially since commit df8fc4e934c1 ("kbuild: Enable
> -fstrict-flex-arrays=3"). Disable the 0-sized and 1-element array
> discovery logic in the plugin, but keep the "true" flexible array check.
>
> Cc: KP Singh <kpsingh@kernel.org>
> Cc: linux-hardening@vger.kernel.org
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202311021532.iBwuZUZ0-lkp@intel.com/
> Fixes: df8fc4e934c1 ("kbuild: Enable -fstrict-flex-arrays=3")
> Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Gustavo A. R. Silva <gustavoars@kernel.org>
Thanks!
--
Gustavo
> ---
> scripts/gcc-plugins/randomize_layout_plugin.c | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff --git a/scripts/gcc-plugins/randomize_layout_plugin.c b/scripts/gcc-plugins/randomize_layout_plugin.c
> index 366395cab490..910bd21d08f4 100644
> --- a/scripts/gcc-plugins/randomize_layout_plugin.c
> +++ b/scripts/gcc-plugins/randomize_layout_plugin.c
> @@ -278,8 +278,6 @@ static bool is_flexible_array(const_tree field)
> {
> const_tree fieldtype;
> const_tree typesize;
> - const_tree elemtype;
> - const_tree elemsize;
>
> fieldtype = TREE_TYPE(field);
> typesize = TYPE_SIZE(fieldtype);
> @@ -287,20 +285,12 @@ static bool is_flexible_array(const_tree field)
> if (TREE_CODE(fieldtype) != ARRAY_TYPE)
> return false;
>
> - elemtype = TREE_TYPE(fieldtype);
> - elemsize = TYPE_SIZE(elemtype);
> -
> /* size of type is represented in bits */
>
> if (typesize == NULL_TREE && TYPE_DOMAIN(fieldtype) != NULL_TREE &&
> TYPE_MAX_VALUE(TYPE_DOMAIN(fieldtype)) == NULL_TREE)
> return true;
>
> - if (typesize != NULL_TREE &&
> - (TREE_CONSTANT(typesize) && (!tree_to_uhwi(typesize) ||
> - tree_to_uhwi(typesize) == tree_to_uhwi(elemsize))))
> - return true;
> -
> return false;
> }
>
next prev parent reply other threads:[~2023-11-06 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 20:43 Kees Cook
2023-11-06 8:47 ` Bill Wendling
2023-11-06 15:53 ` Gustavo A. R. Silva [this message]
2023-11-08 22:20 ` 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=66a8cc44-15fb-457d-bea6-3a67a6a62630@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=kpsingh@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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
all inboxes | Powered by JetHome®