From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-kbuild@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v2] bpf: Remove custom build rule
Date: Wed, 28 Aug 2024 19:49:50 +0200 [thread overview]
Message-ID: <Zs9jPsBY_SNuuB3d@example.org> (raw)
In-Reply-To: <CAK7LNATb8dbhvdSgiNEMkdsgg93q4ZUGUxReZYNjOV3fDPnfyQ@mail.gmail.com>
On Thu, Aug 29, 2024 at 02:22:33AM +0900, Masahiro Yamada wrote:
> On Thu, Aug 29, 2024 at 2:07 AM Alexey Gladkov <legion@kernel.org> wrote:
> >
> > According to the documentation, when building a kernel with the C=2
> > parameter, all source files should be checked. But this does not happen
> > for the kernel/bpf/ directory.
> >
> > $ touch kernel/bpf/core.o
> > $ make C=2 CHECK=true kernel/bpf/core.o
> >
> > Outputs:
> >
> > CHECK scripts/mod/empty.c
> > CALL scripts/checksyscalls.sh
> > DESCEND objtool
> > INSTALL libsubcmd_headers
> > CC kernel/bpf/core.o
> >
> > As can be seen the compilation is done, but CHECK is not executed. This
> > happens because kernel/bpf/Makefile has defined its own rule for
> > compilation and forgotten the macro that does the check.
> >
> > There is no need to duplicate the build code, and this rule can be
> > removed to use generic rules.
> >
> > Signed-off-by: Alexey Gladkov <legion@kernel.org>
>
>
> Did you compile-test this?
Yes. I repeated my steps for reproduce:
$ touch kernel/bpf/core.c
$ make C=2 CHECK=true |grep kernel/bpf/core
CC kernel/bpf/core.o
CHECK kernel/bpf/core.c
but maybe my config is too small.
>
> See my previous email.
>
>
>
>
> I said this:
>
> $ cat kernel/bpf/btf_iter.c
> #include "../../tools/lib/bpf/btf_iter.c"
>
>
> Same for
> kernel/bpf/btf_relocate.c
> kernel/bpf/relo_core.c
>
>
>
>
>
>
>
>
>
>
>
> > ---
> > kernel/bpf/Makefile | 6 ------
> > 1 file changed, 6 deletions(-)
> >
> > diff --git a/kernel/bpf/Makefile b/kernel/bpf/Makefile
> > index 0291eef9ce92..9b9c151b5c82 100644
> > --- a/kernel/bpf/Makefile
> > +++ b/kernel/bpf/Makefile
> > @@ -52,9 +52,3 @@ obj-$(CONFIG_BPF_PRELOAD) += preload/
> > obj-$(CONFIG_BPF_SYSCALL) += relo_core.o
> > obj-$(CONFIG_BPF_SYSCALL) += btf_iter.o
> > obj-$(CONFIG_BPF_SYSCALL) += btf_relocate.o
> > -
> > -# Some source files are common to libbpf.
> > -vpath %.c $(srctree)/kernel/bpf:$(srctree)/tools/lib/bpf
> > -
> > -$(obj)/%.o: %.c FORCE
> > - $(call if_changed_rule,cc_o_c)
> > --
> > 2.46.0
> >
>
>
> --
> Best Regards
> Masahiro Yamada
>
--
Rgrds, legion
next prev parent reply other threads:[~2024-08-28 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 15:25 [PATCH v1] bpf: Add missing force_checksrc macro Alexey Gladkov
2024-08-28 16:32 ` Masahiro Yamada
2024-08-28 17:06 ` [PATCH v2] bpf: Remove custom build rule Alexey Gladkov
2024-08-28 17:22 ` Masahiro Yamada
2024-08-28 17:49 ` Alexey Gladkov [this message]
2024-08-28 18:10 ` [PATCH v3] " Alexey Gladkov
2024-08-28 18:32 ` Masahiro Yamada
2024-08-28 19:14 ` Oleg Nesterov
2024-08-29 10:12 ` Alan Maguire
2024-08-29 19:24 ` Alexei Starovoitov
2024-08-30 7:43 ` [PATCH v4] " Alexey Gladkov
2024-08-30 16:00 ` 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=Zs9jPsBY_SNuuB3d@example.org \
--to=gladkov.alexey@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=oleg@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