From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Kees Cook <keescook@chromium.org>
Cc: Michal Marek <mmarek@suse.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Emese Revfy <re.emese@gmail.com>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Linux-Next <linux-next@vger.kernel.org>,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH] gcc-plugins: disable under COMPILE_TEST
Date: Sat, 11 Jun 2016 12:29:26 -0400 [thread overview]
Message-ID: <20160611162926.GL12567@windriver.com> (raw)
In-Reply-To: <20160611161212.GA29370@www.outflux.net>
[[PATCH] gcc-plugins: disable under COMPILE_TEST] On 11/06/2016 (Sat 09:12) Kees Cook wrote:
> Since adding the gcc plugin development headers is required for the
> gcc plugin support, we should ease into this new kernel build dependency
> more slowly. For now, disable the gcc plugins under COMPILE_TEST so that
> all*config builds will skip it.
Wouldn't it be better to test compile a one line program that tries to
source the header(s) and then react accordingly?
Then at least you would get the test coverage from people who have the
headers installed who are doing all[yes|mod]config. This "for now"
solution doesn't really have a path forward other than assuming all
distros install the plugin headers sometime in the future.
Either way, this is an improvement over the current situation, so thanks
for that.
Paul.
--
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> arch/Kconfig | 1 +
> lib/Kconfig.debug | 4 ++--
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/Kconfig b/arch/Kconfig
> index 83aa2a3c470d..3f06d678b1d7 100644
> --- a/arch/Kconfig
> +++ b/arch/Kconfig
> @@ -366,6 +366,7 @@ config HAVE_GCC_PLUGINS
> menuconfig GCC_PLUGINS
> bool "GCC plugins"
> depends on HAVE_GCC_PLUGINS
> + depends on !COMPILE_TEST
> help
> GCC plugins are loadable modules that provide extra features to the
> compiler. They are useful for runtime instrumentation and static analysis.
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index d40833b9b7f4..0f9981999a27 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -713,8 +713,8 @@ config KCOV
> bool "Code coverage for fuzzing"
> depends on ARCH_HAS_KCOV
> select DEBUG_FS
> - select GCC_PLUGINS
> - select GCC_PLUGIN_SANCOV
> + select GCC_PLUGINS if !COMPILE_TEST
> + select GCC_PLUGIN_SANCOV if !COMPILE_TEST
> help
> KCOV exposes kernel code coverage information in a form suitable
> for coverage-guided fuzzing (randomized testing).
> --
> 2.7.4
>
>
> --
> Kees Cook
> Chrome OS & Brillo Security
next prev parent reply other threads:[~2016-06-11 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 16:12 [PATCH] gcc-plugins: disable under COMPILE_TEST Kees Cook
2016-06-11 16:29 ` Paul Gortmaker [this message]
2016-06-12 22:12 ` Emese Revfy
2016-06-12 22:25 ` Kees Cook
2016-06-13 0:18 ` Emese Revfy
2016-06-13 18:32 ` Austin S. Hemmelgarn
2016-06-13 20:11 ` Kees Cook
2016-06-14 2:01 ` Michael Ellerman
2016-06-13 7:52 ` Sudip Mukherjee
2016-06-13 8:40 ` Sedat Dilek
2016-06-13 20:15 ` Kees Cook
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=20160611162926.GL12567@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=re.emese@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=sudipm.mukherjee@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;
as well as URLs for NNTP newsgroup(s).