From: Jiri Olsa <olsajiri@gmail.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, kernel test robot <lkp@intel.com>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH bpf-next] bpf: Fix build error in case of !CONFIG_DEBUG_INFO_BTF
Date: Fri, 22 Jul 2022 14:40:00 +0200 [thread overview]
Message-ID: <YtqaoIhBY5Fp5iV3@krava> (raw)
In-Reply-To: <20220722113605.6513-1-memxor@gmail.com>
On Fri, Jul 22, 2022 at 01:36:05PM +0200, Kumar Kartikeya Dwivedi wrote:
> BTF_ID_FLAGS macro needs to be able to take 0 or 1 args, so make it a
> variable argument. BTF_SET8_END is incorrect, it should just be empty.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Fixes: ab21d6063c01 ("bpf: Introduce 8-byte BTF set")
> Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
> ---
> include/linux/btf_ids.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/btf_ids.h b/include/linux/btf_ids.h
> index 3cb0741e71d7..2aea877d644f 100644
> --- a/include/linux/btf_ids.h
> +++ b/include/linux/btf_ids.h
> @@ -206,7 +206,7 @@ extern struct btf_id_set8 name;
>
> #define BTF_ID_LIST(name) static u32 __maybe_unused name[5];
> #define BTF_ID(prefix, name)
> -#define BTF_ID_FLAGS(prefix, name, flags)
> +#define BTF_ID_FLAGS(prefix, name, ...)
> #define BTF_ID_UNUSED
> #define BTF_ID_LIST_GLOBAL(name, n) u32 __maybe_unused name[n];
> #define BTF_ID_LIST_SINGLE(name, prefix, typename) static u32 __maybe_unused name[1];
> @@ -215,7 +215,7 @@ extern struct btf_id_set8 name;
> #define BTF_SET_START_GLOBAL(name) static struct btf_id_set __maybe_unused name = { 0 };
> #define BTF_SET_END(name)
> #define BTF_SET8_START(name) static struct btf_id_set8 __maybe_unused name = { 0 };
> -#define BTF_SET8_END(name) static struct btf_id_set8 __maybe_unused name = { 0 };
> +#define BTF_SET8_END(name)
>
> #endif /* CONFIG_DEBUG_INFO_BTF */
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-07-22 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 11:36 [PATCH bpf-next] bpf: Fix build error in case of !CONFIG_DEBUG_INFO_BTF Kumar Kartikeya Dwivedi
2022-07-22 12:40 ` Jiri Olsa [this message]
2022-07-22 16:10 ` 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=YtqaoIhBY5Fp5iV3@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=lkp@intel.com \
--cc=memxor@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 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.