From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: pageexec@freemail.hu, Emese Revfy <re.emese@gmail.com>,
kernel-hardening@lists.openwall.com,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-kbuild@vger.kernel.org, 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: Fri, 20 May 2016 16:22:03 +1000 [thread overview]
Message-ID: <573EAD0B.7090005@au1.ibm.com> (raw)
In-Reply-To: <573D782D.10392.75A275C@pageexec.freemail.hu>
On 19/05/16 18:24, PaX Team wrote:
> the earlier plugin capable gcc versions used to install gcc headers in a somewhat
> ad-hoc manner resulting in compile time breakage for plugins and since some of
> those potentially missing headers are target specific, each target arch should
> be verified before enabling plugin support on them. things have much improved with
> gcc 5 (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61176) though there's still
> an occasional missing header but with wider use of plugins they will hopefully be
> discovered earlier now. perhaps linux-arch should be cc'ed on the plugin infrastructure
> so that arch maintainers are aware of this?
Upon further testing it does seem we've got header issues as well as
hitting a segfault on 4.7.0. Looking into it further...
--
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnellan@au1.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2016-05-20 6:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 23:54 [kernel-hardening] [PATCH v8 0/4] Introduce GCC plugin infrastructure Emese Revfy
2016-05-12 23:54 ` Emese Revfy
2016-05-12 23:56 ` [kernel-hardening] [PATCH v8 1/4] Shared library support Emese Revfy
2016-05-12 23:56 ` Emese Revfy
2016-05-12 23:57 ` [kernel-hardening] [PATCH v8 2/4] GCC plugin infrastructure Emese Revfy
2016-05-12 23:57 ` Emese Revfy
2016-05-17 14:28 ` [kernel-hardening] " Michal Marek
2016-05-17 14:28 ` Michal Marek
2016-05-18 10:56 ` [kernel-hardening] " Emese Revfy
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
2016-05-19 6:30 ` Andrew Donnellan
2016-05-19 8:24 ` PaX Team
2016-05-19 8:24 ` PaX Team
2016-05-20 6:22 ` Andrew Donnellan [this message]
2016-05-20 10:10 ` Michael Ellerman
2016-05-12 23:58 ` [kernel-hardening] [PATCH v8 3/4] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-05-12 23:58 ` Emese Revfy
2016-05-18 8:25 ` [kernel-hardening] " Andrew Donnellan
2016-05-18 10:53 ` Emese Revfy
2016-05-12 23:59 ` [kernel-hardening] [PATCH v8 4/4] Add sancov plugin Emese Revfy
2016-05-12 23:59 ` 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=573EAD0B.7090005@au1.ibm.com \
--to=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=mpe@ellerman.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.