From: Michael Ellerman <mpe@ellerman.id.au>
To: Emese Revfy <re.emese@gmail.com>, kernel-hardening@lists.openwall.com
Cc: Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
linux-kbuild@vger.kernel.org, pageexec@freemail.hu,
spender@grsecurity.net, mmarek@suse.com, keescook@chromium.org,
linux@rasmusvillemoes.dk, fengguang.wu@intel.com,
dvyukov@google.com, linux-kernel@vger.kernel.org,
david.brown@linaro.org, yamada.masahiro@socionext.com,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Daniel Axtens <dja@axtens.net>
Subject: Re: [kernel-hardening] [PATCH v8 2/4] GCC plugin infrastructure
Date: Thu, 19 May 2016 16:22:11 +1000 [thread overview]
Message-ID: <1463638931.10451.10.camel@ellerman.id.au> (raw)
In-Reply-To: <20160518123327.9018f73af78a47b4456b2027@gmail.com>
On Wed, 2016-05-18 at 12:33 +0200, Emese Revfy wrote:
> > I've done some basic sanity testing on powerpc with the cyclomatic
> > complexity plugin (with LE native + cross-compilers) and it seems to
> > work with the patch below.
> >
> > Signed-off-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
> >
> > diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> > index a18a0dc..0cfed5b 100644
> > --- a/arch/powerpc/Kconfig
> > +++ b/arch/powerpc/Kconfig
> > @@ -97,6 +97,7 @@ config PPC
> > select HAVE_DYNAMIC_FTRACE_WITH_REGS if MPROFILE_KERNEL
> > select HAVE_FUNCTION_TRACER
> > select HAVE_FUNCTION_GRAPH_TRACER
> > + select HAVE_GCC_PLUGINS
> > select SYSCTL_EXCEPTION_TRACE
> > select ARCH_WANT_OPTIONAL_GPIOLIB
> > select VIRT_TO_BUS if !PPC64
>
> Hi,
>
> Did you test the plugins with all gcc versions (4.5-6)?
What's the concern about gcc versions? Just not breaking the build on old
compilers?
I'm pretty sure powerpc big endian still builds with gcc 4.4.
However if Andrew's only tested on little endian, then that select should be
guarded with an "if CPU_LITTLE_ENDIAN". And to build LE you need gcc >= 4.9.
cheers
next prev parent reply other threads:[~2016-05-19 6:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 23:54 [PATCH v8 0/4] Introduce GCC plugin infrastructure Emese Revfy
2016-05-12 23:56 ` [PATCH v8 1/4] Shared library support Emese Revfy
2016-05-12 23:57 ` [PATCH v8 2/4] GCC plugin infrastructure Emese Revfy
2016-05-17 14:28 ` Michal Marek
2016-05-18 10:56 ` Emese Revfy
2016-05-18 8:51 ` [kernel-hardening] " Andrew Donnellan
2016-05-18 10:33 ` Emese Revfy
2016-05-18 21:14 ` Andrew Donnellan
2016-05-19 6:22 ` Michael Ellerman [this message]
2016-05-19 6:30 ` Andrew Donnellan
2016-05-19 8:24 ` PaX Team
2016-05-20 6:22 ` Andrew Donnellan
2016-05-20 10:10 ` Michael Ellerman
2016-05-12 23:58 ` [PATCH v8 3/4] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-05-18 8:25 ` [kernel-hardening] " Andrew Donnellan
2016-05-18 10:53 ` Emese Revfy
2016-05-12 23:59 ` [PATCH v8 4/4] Add sancov plugin Emese Revfy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1463638931.10451.10.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=andrew.donnellan@au1.ibm.com \
--cc=david.brown@linaro.org \
--cc=dja@axtens.net \
--cc=dvyukov@google.com \
--cc=fengguang.wu@intel.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mmarek@suse.com \
--cc=pageexec@freemail.hu \
--cc=re.emese@gmail.com \
--cc=spender@grsecurity.net \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox