From: Alan Maguire <alan.maguire@oracle.com>
To: Paul Chaignon <paul.chaignon@gmail.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>
Subject: Re: [PATCH bpf] tools/headers: Regenerate stddef.h to fix BPF selftests
Date: Sat, 2 May 2026 15:43:45 +0100 [thread overview]
Message-ID: <2ea5449d-70f8-4e7b-a7d9-d3cbcfdda5b7@oracle.com> (raw)
In-Reply-To: <8da8ef16055aa452d940668ed5359ce54adc6b0b.1777715500.git.paul.chaignon@gmail.com>
On 02/05/2026 11:12, Paul Chaignon wrote:
> With commit dacbfc167808 ("crypto: af_alg - Annotate struct af_alg_iv
> with __counted_by"), two selftests, test_tag and crypto_sanity, now
> indirectly rely on the __counted_by macro. On systems with commit
> dacbfc167808 in the installed UAPI headers, the selftests build fails
> with:
>
> In file included from tools/testing/selftests/bpf/prog_tests/crypto_sanity.c:7:
> /usr/include/linux/if_alg.h:45:22: error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘__counted_by’
> 45 | __u8 iv[] __counted_by(ivlen);
> | ^~~~~~~~~~~~
>
> This patch fixes it by regenerating stddef.h in tools/include using the
> instructions from commit a778f5d46b62 ("tools/headers: Pull in stddef.h
> to uapi to fix BPF selftests build in CI").
>
> Fixes: dacbfc167808 ("crypto: af_alg - Annotate struct af_alg_iv with __counted_by")
> Signed-off-by: Paul Chaignon <paul.chaignon@gmail.com>
Thanks for the fix!
Reviewed-by: Alan Maguire <alan.maguire@oracle.com>
> ---
> I'm a bit unsure if this should go to bpf or bpf-next, but it currently
> applies cleanly to both.
>
> tools/include/uapi/linux/stddef.h | 26 +++++++++++++++++++++++++-
> 1 file changed, 25 insertions(+), 1 deletion(-)
>
> diff --git a/tools/include/uapi/linux/stddef.h b/tools/include/uapi/linux/stddef.h
> index c53cde425406..457498259494 100644
> --- a/tools/include/uapi/linux/stddef.h
> +++ b/tools/include/uapi/linux/stddef.h
> @@ -3,7 +3,6 @@
> #define _LINUX_STDDEF_H
>
>
> -
> #ifndef __always_inline
> #define __always_inline __inline__
> #endif
> @@ -36,6 +35,11 @@
> struct __struct_group_tag(TAG) { MEMBERS } ATTRS NAME; \
> } ATTRS
>
> +#ifdef __cplusplus
> +/* sizeof(struct{}) is 1 in C++, not 0, can't use C version of the macro. */
> +#define __DECLARE_FLEX_ARRAY(T, member) \
> + T member[0]
> +#else
> /**
> * __DECLARE_FLEX_ARRAY() - Declare a flexible array usable in a union
> *
> @@ -52,3 +56,23 @@
> TYPE NAME[]; \
> }
> #endif
> +
> +#ifndef __counted_by
> +#define __counted_by(m)
> +#endif
> +
> +#ifndef __counted_by_le
> +#define __counted_by_le(m)
> +#endif
> +
> +#ifndef __counted_by_be
> +#define __counted_by_be(m)
> +#endif
> +
> +#ifndef __counted_by_ptr
> +#define __counted_by_ptr(m)
> +#endif
> +
> +#define __kernel_nonstring
> +
> +#endif /* _LINUX_STDDEF_H */
next prev parent reply other threads:[~2026-05-02 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 10:12 [PATCH bpf] tools/headers: Regenerate stddef.h to fix BPF selftests Paul Chaignon
2026-05-02 14:43 ` Alan Maguire [this message]
2026-05-02 16:05 ` Ihor Solodrai
2026-05-02 16:40 ` patchwork-bot+netdevbpf
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=2ea5449d-70f8-4e7b-a7d9-d3cbcfdda5b7@oracle.com \
--to=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=memxor@gmail.com \
--cc=paul.chaignon@gmail.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