From: Yonghong Song <yhs@meta.com>
To: Rong Tao <rtoax@foxmail.com>, davem@davemloft.net
Cc: Rong Tao <rongtao@cestc.cn>, Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:BPF [MISC]" <bpf@vger.kernel.org>
Subject: Re: [PATCH] net/ipv4: Fix error: type name requires a specifier or qualifier
Date: Thu, 10 Nov 2022 08:59:26 -0800 [thread overview]
Message-ID: <4ed2ebee-26a8-f0ab-2bc4-a0b6a29768af@meta.com> (raw)
In-Reply-To: <tencent_3E0335A1CE2C91CB09159057B15138441F07@qq.com>
On 11/10/22 7:17 AM, Rong Tao wrote:
> From: Rong Tao <rongtao@cestc.cn>
>
> since commit 5854a09b4957("net/ipv4: Use __DECLARE_FLEX_ARRAY() helper")
> linux/in.h use __DECLARE_FLEX_ARRAY() macro, and sync to tools/ in commit
> 036b8f5b8970("tools headers uapi: Update linux/in.h copy"), this macro
> define in linux/stddef.h, which introduced in commit 3080ea5553cc("stddef:
> Introduce DECLARE_FLEX_ARRAY() helper"), thus, stddef.h should be included
> in in.h, which resolves the compilation error below:
>
> How to reproduce this compilation error:
>
> $ make -C tools/testing/selftests/bpf/
> In file included from progs/bpf_flow.c:8:
> linux/in.h:199:3: error: type name requires a specifier or qualifier
> __DECLARE_FLEX_ARRAY(__be32, imsf_slist_flex);
> ^
> linux/in.h:199:32: error: type specifier missing, defaults to 'int' [-Werror,-Wimplicit-int]
> __DECLARE_FLEX_ARRAY(__be32, imsf_slist_flex);
> ^
> 2 errors generated.
>
> Same error occurs with cgroup_skb_sk_lookup_kern.c, connect_force_port4.c,
> connect_force_port6.c, etc. that contain the header linux/in.h.
It has been fixed in bpf tree:
https://lore.kernel.org/bpf/20221102182517.2675301-1-andrii@kernel.org/
The fix will be merged to bpf-next once it reached to linus tree and
went back to bpf-next.
At the same time, you can workaround the issue locally.
>
> Signed-off-by: Rong Tao <rongtao@cestc.cn>
> ---
> include/uapi/linux/in.h | 1 +
> tools/include/uapi/linux/in.h | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/include/uapi/linux/in.h b/include/uapi/linux/in.h
> index f243ce665f74..07a4cb149305 100644
> --- a/include/uapi/linux/in.h
> +++ b/include/uapi/linux/in.h
> @@ -20,6 +20,7 @@
> #define _UAPI_LINUX_IN_H
>
> #include <linux/types.h>
> +#include <linux/stddef.h>
> #include <linux/libc-compat.h>
> #include <linux/socket.h>
>
> diff --git a/tools/include/uapi/linux/in.h b/tools/include/uapi/linux/in.h
> index f243ce665f74..07a4cb149305 100644
> --- a/tools/include/uapi/linux/in.h
> +++ b/tools/include/uapi/linux/in.h
> @@ -20,6 +20,7 @@
> #define _UAPI_LINUX_IN_H
>
> #include <linux/types.h>
> +#include <linux/stddef.h>
> #include <linux/libc-compat.h>
> #include <linux/socket.h>
>
next prev parent reply other threads:[~2022-11-10 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 15:17 [PATCH] net/ipv4: Fix error: type name requires a specifier or qualifier Rong Tao
2022-11-10 16:59 ` Yonghong Song [this message]
2022-11-11 2:18 ` [PATCH] lib/radix-tree: Fix uninitialized variable compilation Rong Tao
2022-11-11 3:49 ` Yonghong Song
2022-11-11 2:23 ` The subject of the previous email error Rong Tao
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=4ed2ebee-26a8-f0ab-2bc4-a0b6a29768af@meta.com \
--to=yhs@meta.com \
--cc=acme@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.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