linux-kernel - Re: linux-next: build warnings after merge of the kbuild tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20160609193736.db48229a82b9fad7de1562d9@gmail.com>
Date:	Thu, 9 Jun 2016 19:37:36 +0200
From:	Emese Revfy <re.emese@...il.com>
To:	Michal Marek <mmarek@...e.cz>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Kees Cook <keescook@...omium.org>,
	Linux-Next <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of the kbuild tree

On Thu, 9 Jun 2016 12:57:16 +0200
Michal Marek <mmarek@...e.cz> wrote:

> Dne 9.6.2016 v 06:05 Stephen Rothwell napsal(a):
> > On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook <keescook@...omium.org> wrote:
> >> Ah, yes, that should default to off. We'll get a fix landed ASAP.
> > 
> > Note that this was an allmodconfig build.  The default is 'n', but
> > allmodconfig will turn it on (as will allyesconfig).
> 
> I guess we should make GCC_PLUGINS depend on !COMPILE_TEST. Actually I
> thought this was already the case, but it is not.

Is it really necessary to disable all gcc plugins or would it be enough
to disable only the cyc_complexity plugin?

-- 
Emese