[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUW-OZMh2foyiQK=0NfakwbiFHTkouMjptgokKTFLZQFQQ@mail.gmail.com>
Date: Mon, 13 Jun 2016 10:40:11 +0200
From: Sedat Dilek <sedat.dilek@...il.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>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Linux-Next <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
kernel-hardening@...ts.openwall.com
Subject: Re: [PATCH] gcc-plugins: disable under COMPILE_TEST
On Sat, Jun 11, 2016 at 6:12 PM, Kees Cook <keescook@...omium.org> 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.
>
[ This might be a bit off-topic - Feel free to answer ]
Hi,
I want to try that new "GCC-plugin" feature.
Do you have a Git repo for "easy-testing"?
Does the kernel's build-system check for installed "gcc-plugin
development headers"?
Which GCC versions support "gcc-plugin" feature?
I am here on Ubuntu/precise AMD64 and have gcc-4.6.4 and gcc-4.9.2.
[ Optional ]
What about the topic and support for "LLVM/Clang and hardening" of the
Linux-kernel?
Regards,
- Sedat -
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-next" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists