From: Xiao Yang <ice_yangxiao@163.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: Will Deacon <will@kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: Question about "asm/rwonce.h: No such file or directory"
Date: Wed, 13 Nov 2019 22:55:30 +0800 [thread overview]
Message-ID: <bdbe9e04-4da0-64b2-ab0c-ae739d8fd7ac@163.com> (raw)
In-Reply-To: <CAK7LNAQ8h7zxhfndBqYRWXkaWVynH7GpBvDPLcVMZ1VEyUUX7A@mail.gmail.com>
On 11/13/19 4:54 PM, Masahiro Yamada wrote:
> On Wed, Nov 13, 2019 at 5:36 PM Xiao Yang <ice_yangxiao@163.com> wrote:
>> On 11/13/19 3:53 PM, Masahiro Yamada wrote:
>>> On Wed, Nov 13, 2019 at 4:17 PM Xiao Yang <ice_yangxiao@163.com> wrote:
>>>> On 11/13/19 2:57 PM, Masahiro Yamada wrote:
>>>>> Sorry, I really do not understand what you are doing.
>>>>>
>>>>> include/linux/compiler.h is only for kernel-space.
>>>>> Shrug if a user-land program includes it.
>>>> Hi Masahiro,
>>>>
>>>> For building tools/bpf, it is good to fix the compiler error by Daniel's
>>>> patch(i.e. use linux/filter from linux header).
>>>>
>>>> linux/compiler.h may be used by other code in kernel. Is it possible to
>>>> trigger the same error when the other code
>>>>
>>>> including linux/compiler.h is built? Is this kind of code able to find
>>>> the location of <asm/rwonce.h>?
>>> <asm/rwonce.h> is also kernel-only header.
>>>
>>> The kernel code can find <asm/rwonce.h>, but user-land code cannot.
>> Hi Masahiro,
>>
>> Sorry, I am not familar with it.
>>
>> Thanks a lot for your explanation and I have seen the LINUXINCLUDE
>> variable in Makefile.
>>
>> I will try to send a patch as Daniel suggested.
>>
>> Best Regards,
>>
>> Xiao Yang
>>
> Hmm, digging into the git history,
> this include path was added by the following commit:
>
>
> commit d7475de58575c904818efa369c82e88c6648ce2e
> Author: Kamal Mostafa <kamal@canonical.com>
> Date: Wed Nov 11 14:24:27 2015 -0800
>
> tools/net: Use include/uapi with __EXPORTED_HEADERS__
>
> Use the local uapi headers to keep in sync with "recently" added #define's
> (e.g. SKF_AD_VLAN_TPID). Refactored CFLAGS, and bpf_asm doesn't need -I.
>
> Fixes: 3f356385e8a4 ("filter: bpf_asm: add minimal bpf asm tool")
> Signed-off-by: Kamal Mostafa <kamal@canonical.com>
> Acked-by: Daniel Borkmann <daniel@iogearbox.net>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
>
>
> I am not sure how big a deal it is,
> but it could be a problem on old distros??
>
Hi Daniel, Masahiro
Could we include the linux/filter.h generated by "make headers_install"
as a higher priority?
(PS: According to above commit, just ensure that tools/bpf keeps in sync
with new linux header as far as possible).
and then use the linux/filter.h in system if kernel doesn't provide
linux/filter.h by "make headers_install".
--------------------------------------------------------------------------------------------------------------------
diff --git a/tools/bpf/Makefile b/tools/bpf/Makefile
index 5d1995fd369c..1e0c768132af 100644
--- a/tools/bpf/Makefile
+++ b/tools/bpf/Makefile
@@ -10,7 +10,7 @@ MAKE = make
INSTALL ?= install
CFLAGS += -Wall -O2
-CFLAGS += -D__EXPORTED_HEADERS__ -I$(srctree)/include/uapi
-I$(srctree)/include
+CFLAGS += -I$(srctree)/usr/include
# This will work when bpf is built in tools env. where srctree
# isn't set and when invoked from selftests build, where srctree
---------------------------------------------------------------------------------------------------------------------
Best Regards,
Xiao Yang
>
next prev parent reply other threads:[~2019-11-13 14:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1da2db04-da6a-cedb-e85a-6ded68dada82@163.com>
2019-11-12 12:31 ` Will Deacon
2019-11-12 12:50 ` Masahiro Yamada
2019-11-12 15:13 ` Daniel Borkmann
2019-11-13 3:44 ` Xiao Yang
2019-11-13 5:28 ` Masahiro Yamada
2019-11-13 5:51 ` Xiao Yang
2019-11-13 6:57 ` Masahiro Yamada
2019-11-13 7:16 ` Xiao Yang
2019-11-13 7:53 ` Masahiro Yamada
2019-11-13 8:35 ` Xiao Yang
2019-11-13 8:54 ` Masahiro Yamada
2019-11-13 14:55 ` Xiao Yang [this message]
2019-11-13 15:48 ` Masahiro Yamada
2019-11-13 0:59 ` Xiao Yang
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=bdbe9e04-4da0-64b2-ab0c-ae739d8fd7ac@163.com \
--to=ice_yangxiao@163.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@kernel.org \
--cc=yamada.masahiro@socionext.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®