[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160621125807.GA19065@infradead.org>
Date: Tue, 21 Jun 2016 05:58:07 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Emese Revfy <re.emese@...il.com>
Cc: kernel-hardening@...ts.openwall.com, pageexec@...email.hu,
spender@...ecurity.net, mmarek@...e.com, keescook@...omium.org,
linux-kernel@...r.kernel.org, yamada.masahiro@...ionext.com,
linux-kbuild@...r.kernel.org, tytso@....edu,
akpm@...ux-foundation.org, linux-mm@...ck.org, axboe@...nel.dk,
viro@...iv.linux.org.uk, paulmck@...ux.vnet.ibm.com,
mingo@...hat.com, tglx@...utronix.de, bart.vanassche@...disk.com,
davem@...emloft.net
Subject: Re: [PATCH v4 2/4] Add the latent_entropy gcc plugin
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@...email.hu>
> + * Copyright 2016 by Emese Revfy <re.emese@...il.com>
> + * 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?
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.
