From: Kees Cook <keescook@chromium.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, Emese Revfy <re.emese@gmail.com>,
Michal Marek <michal.lkml@markovi.net>,
kernel-hardening@lists.openwall.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] kbuild: move shared library build rules to scripts/gcc-plugins/Makefile
Date: Wed, 29 Jul 2020 14:18:17 -0700 [thread overview]
Message-ID: <202007291401.A50E25BB@keescook> (raw)
In-Reply-To: <20200729031537.37926-1-masahiroy@kernel.org>
On Wed, Jul 29, 2020 at 12:15:36PM +0900, Masahiro Yamada wrote:
> The shared library build rules are currently implemented in
> scripts/Makefile.host, but actually GCC-plugin is the only user of
> them. Hence, they do not need to be treewide available.
Are none of the VDSOs intending to use these rules?
> Move all the relevant build rules to scripts/gcc-plugins/Makefile.
>
> I also optimized the build steps so *.so is directly built from .c
> because every upstream plugin is compiled from a single source file.
>
> I am still keeping the infrastructure to build a plugin from multiple
> files because Kees suggested to do so in my previous attempt.
> (https://lkml.org/lkml/2019/1/11/1107)
>
> If the plugin, foo.so, is compiled from two files foo.c and foo2.c,
> then you can do like follows:
>
> foo-objs := foo.o foo2.o
>
> Single-file plugins do not need the *-objs notation.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
But, yeah, sure!
Acked-by: Kees Cook <keescook@chromium.org>
Unrelated, but I do note that objtool maybe has the wrong indentation,
path name reporting, and tool names (HOSTLD vs CC)?
...
HOSTCC scripts/asn1_compiler
HOSTCC scripts/extract-cert
HOSTCC scripts/genksyms/genksyms.o
YACC scripts/genksyms/parse.tab.[ch]
LEX scripts/genksyms/lex.lex.c
DESCEND objtool
HOSTCXX scripts/gcc-plugins/cyc_complexity_plugin.so
HOSTCXX scripts/gcc-plugins/latent_entropy_plugin.so
HOSTCXX scripts/gcc-plugins/structleak_plugin.so
GENSEED scripts/gcc-plugins/randomize_layout_seed.h
HOSTCXX scripts/gcc-plugins/stackleak_plugin.so
HOSTCC scripts/genksyms/parse.tab.o
HOSTCC scripts/genksyms/lex.lex.o
HOSTCC /home/kees/src/linux-build/plugins/tools/objtool/fixdep.o
HOSTLD arch/x86/tools/relocs
HOSTLD /home/kees/src/linux-build/plugins/tools/objtool/fixdep-in.o
LINK /home/kees/src/linux-build/plugins/tools/objtool/fixdep
CC /home/kees/src/linux-build/plugins/tools/objtool/exec-cmd.o
CC /home/kees/src/linux-build/plugins/tools/objtool/help.o
CC /home/kees/src/linux-build/plugins/tools/objtool/weak.o
...
--
Kees Cook
next prev parent reply other threads:[~2020-07-29 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 3:15 [PATCH 1/2] kbuild: move shared library build rules to scripts/gcc-plugins/Makefile Masahiro Yamada
2020-07-29 3:15 ` [PATCH 2/2] kbuild: sort hostprogs before passing it to ifneq Masahiro Yamada
2020-07-29 21:18 ` Kees Cook [this message]
2020-07-31 4:16 ` [PATCH 1/2] kbuild: move shared library build rules to scripts/gcc-plugins/Makefile Masahiro Yamada
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=202007291401.A50E25BB@keescook \
--to=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=re.emese@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