On Tue, Jun 21, 2016 at 5:58 AM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > On Mon, Jun 20, 2016 at 08:41:19PM +0200, Emese Revfy wrote: >> --- /dev/null >> +++ b/scripts/gcc-plugins/latent_entropy_plugin.c >> @@ -0,0 +1,639 @@ >> +/* >> + * Copyright 2012-2016 by the PaX Team <pageexec@xxxxxxxxxxx> >> + * Copyright 2016 by Emese Revfy <re.emese@xxxxxxxxx> >> + * Licensed under the GPL v2 >> + * >> + * Note: the choice of the license means that the compilation process is >> + * NOT 'eligible' as defined by gcc's library exception to the GPL v3, >> + * but for the kernel it doesn't matter since it doesn't link against >> + * any of the gcc libraries > > I remember we used to have architectures that actually linked against > libgcc. Isn't that the case anymore? There are a few, but they don't (and won't) select HAVE_GCC_PLUGINS. -Kees -- Kees Cook Chrome OS & Brillo Security -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>