[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160611162926.GL12567@windriver.com>
Date: Sat, 11 Jun 2016 12:29:26 -0400
From: Paul Gortmaker <paul.gortmaker@...driver.com>
To: Kees Cook <keescook@...omium.org>
CC: Michal Marek <mmarek@...e.com>, Stephen Rothwell <sfr@...b.auug.org.au>,
Emese Revfy <re.emese@...il.com>,
Sudip Mukherjee
<sudipm.mukherjee@...il.com>,
Linux-Next <linux-next@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH] gcc-plugins: disable under COMPILE_TEST
[[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@...omium.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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
