[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jLxN65Z-+Miiju3VcOK7fpWKqAQY6hn6u5KTZm_NP54kQ@mail.gmail.com>
Date: Wed, 8 Jun 2016 19:56:38 -0700
From: Kees Cook <keescook@...omium.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Michal Marek <mmarek@...e.cz>,
Linux-Next <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Emese Revfy <re.emese@...il.com>
Subject: Re: linux-next: build warnings after merge of the kbuild tree
On Wed, Jun 8, 2016 at 7:22 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Michal,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> Cyclomatic Complexity 1 scripts/mod/devicetable-offsets.c:main
> Cyclomatic Complexity 1 kernel/bounds.c:foo
> Cyclomatic Complexity 1 arch/x86/kernel/asm-offsets_64.c:main
> Cyclomatic Complexity 1 arch/x86/kernel/asm-offsets.c:common
> Cyclomatic Complexity 5 arch/x86/ia32/audit.c:ia32_classify_syscall
>
> and so on (many, many of these - about 635,000 :-()
Congratulations on having the gcc plugin development headers
successfully installed! ;)
> Introduced (presumably) by commits
>
> 6b90bd4ba40b ("GCC plugin infrastructure")
> 0dae776c6bf3 ("Add Cyclomatic complexity GCC plugin")
>
> I have disabled CONFIG_GCC_PLUGIN_CYC_COMPLEXITY (by making it depend
> on CONFIG_BROKEN) until it is not enabled by default.
Ah, yes, that should default to off. We'll get a fix landed ASAP.
-Kees
--
Kees Cook
Chrome OS & Brillo Security
Powered by blists - more mailing lists