From: David Laight <david.laight.linux@gmail.com>
To: Bill Wendling <morbo@google.com>
Cc: Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] overflow: Match arithmetic in both parts of __builtin_choose_expr
Date: Wed, 14 Oct 2026 13:38:05 +0100 [thread overview]
Message-ID: <20261014133805.47afdb0b@pumpkin> (raw)
In-Reply-To: <20261013203146.387344-1-morbo@google.com>
On Tue, 13 Oct 2026 20:31:46 +0000
Bill Wendling <morbo@google.com> wrote:
> The two parts of '__builtin_choose_expr()' had different arithmetic
> expressions. This patch corrects it so that both parts calculate:
>
> COUNT * sizeof(*MEMBER) + __must_be_array(MEMBER)
>
> In practice, '__must_be_array' is meant to assert if 'MEMBER' isn't an
> array and return '0' otherwise. However, symmetry is less prone to
> subtle errors (and far more satisfying).
>
> Signed-off-by: Bill Wendling <morbo@google.com>
> ---
> v2: Don't use 'size_add', which just adds more complicated macro cruft to the
> expression. Instead, just adjust the parentheses.
> ---
> include/linux/overflow.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/overflow.h b/include/linux/overflow.h
> index a8cb6319b4fb..d0f04436343e 100644
> --- a/include/linux/overflow.h
> +++ b/include/linux/overflow.h
> @@ -418,7 +418,7 @@ static __always_inline size_t __must_check size_sub(size_t minuend, size_t subtr
> #define flex_array_size(p, member, count) \
> __builtin_choose_expr(__is_constexpr(count), \
> (count) * sizeof(*(p)->member) + __must_be_array((p)->member), \
> - size_mul(count, sizeof(*(p)->member) + __must_be_array((p)->member)))
> + size_mul(count, sizeof(*(p)->member)) + __must_be_array((p)->member))
Why does this use __builtin_choose_expr().
The types of the two expressions are the same so it might as well use ?:
Also doesn't this optimisation apply to all uses of size_mul() (aka saturating_mul()).
Presumably relying on the compiler to report the compilation time numeric overflow.
David
>
> /**
> * struct_size() - Calculate size of structure with trailing flexible array.
next prev parent reply other threads:[~2026-10-14 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 20:59 [PATCH] " Bill Wendling
2026-10-13 3:30 ` Kees Cook
2026-10-13 17:17 ` Bill Wendling
2026-10-13 20:31 ` [PATCH v2] " Bill Wendling
2026-10-14 12:38 ` David Laight [this message]
2026-10-14 20:39 ` Bill Wendling
2026-10-15 10:00 ` David Laight
2026-10-15 1:06 ` 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=20261014133805.47afdb0b@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morbo@google.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®