Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Date: Mon, 13 Jun 2016 13:15:40 -0700
From: Kees Cook <>
To: Sedat Dilek <>
Cc: Michal Marek <>, Stephen Rothwell <>, 
	Emese Revfy <>, Paul Gortmaker <>, 
	Sudip Mukherjee <>, Linux-Next <>, 
	LKML <>, 
	"" <>
Subject: Re: [PATCH] gcc-plugins: disable under COMPILE_TEST

On Mon, Jun 13, 2016 at 1:40 AM, Sedat Dilek <> wrote:
> On Sat, Jun 11, 2016 at 6:12 PM, 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.
> [ 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"?

Start with linux-next. It has the basic infrastructure. The
"latent_entropy" plugin is in my kssp tree here:
though it is not the most up to date version.

> Does the kernel's build-system check for installed "gcc-plugin
> development headers"?

Yes, when the plugins have been selected.

> Which GCC versions support "gcc-plugin" feature?

gcc-4.5 and newer.

> I am here on Ubuntu/precise AMD64 and have gcc-4.6.4 and gcc-4.9.2.

I strongly recommend upgrading to Ubuntu 16.04, but regardless, using
gcc 4.9 should be fine.

> [ Optional ]
> What about the topic and support for "LLVM/Clang and hardening" of the
> Linux-kernel?

I haven't been involved in that project, sorry.


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.