From: Kees Cook <kees@kernel.org>
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
linux-kernel@vger.kernel.org, linux-sparse@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>
Subject: Re: [PATCH v2] build_bug.h: more user friendly error messages in BUILD_BUG_ON_ZERO()
Date: Mon, 7 Apr 2025 09:46:39 -0700 [thread overview]
Message-ID: <202504070945.BAC93C0@keescook> (raw)
In-Reply-To: <20250329-build_bug-v2-1-1c831e5ddf89@wanadoo.fr>
On Sat, Mar 29, 2025 at 01:48:50AM +0900, Vincent Mailhol wrote:
> __BUILD_BUG_ON_ZERO_MSG(), as introduced in [1], makes it possible to
> do a static assertions in expressions. The direct benefit is to
> provide a meaningful error message instead of the cryptic negative
> bitfield size error message currently returned by BUILD_BUG_ON_ZERO():
>
> ./include/linux/build_bug.h:16:51: error: negative width in bit-field '<anonymous>'
> 16 | #define BUILD_BUG_ON_ZERO(e) ((int)(sizeof(struct { int:(-!!(e)); })))
> | ^
>
> Get rid of BUILD_BUG_ON_ZERO()'s bitfield size hack. Instead rely on
> __BUILD_BUG_ON_ZERO_MSG() which in turn relies on C11's
> _Static_assert().
>
> Use some macro magic, similarly to static_assert(), to either use an
> optional error message provided by the user or, when omitted, to
> produce a default error message by stringifying the tested
> expression. With this, for example:
>
> BUILD_BUG_ON_ZERO(1 > 0)
>
> would now throw:
>
> ./include/linux/compiler.h:197:62: error: static assertion failed: "1 > 0 is true"
This is so much easier to read! Thanks for this. :)
If no one else snags it, I can take this via the hardening tree for
-next once -rc2 is released.
--
Kees Cook
next prev parent reply other threads:[~2025-04-07 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 16:48 [PATCH v2] build_bug.h: more user friendly error messages in BUILD_BUG_ON_ZERO() Vincent Mailhol
2025-04-07 16:46 ` Kees Cook [this message]
2025-04-08 13:23 ` Vincent Mailhol
2025-04-08 19:03 ` Kees Cook
2025-04-09 12:26 ` Vincent Mailhol
2025-04-09 14:17 ` Yury Norov
2025-04-09 16:14 ` Kees Cook
2025-04-14 21:55 ` Yury Norov
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=202504070945.BAC93C0@keescook \
--to=kees@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=mailhol.vincent@wanadoo.fr \
--cc=masahiroy@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=pbonzini@redhat.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