From: Michal Marek <mmarek@suse.com>
To: Kees Cook <keescook@chromium.org>
Cc: Emese Revfy <re.emese@gmail.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
PaX Team <pageexec@freemail.hu>,
Brad Spengler <spender@grsecurity.net>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Fengguang Wu <fengguang.wu@intel.com>,
Dmitry Vyukov <dvyukov@google.com>,
LKML <linux-kernel@vger.kernel.org>,
David Brown <david.brown@linaro.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: [PATCH v9 0/4] Introduce GCC plugin infrastructure
Date: Tue, 7 Jun 2016 22:58:01 +0200 [thread overview]
Message-ID: <57573559.1010607@suse.com> (raw)
In-Reply-To: <CAGXu5jKw_oQNCVUH+o_k-W+5Z7LDXgJ3UpP24a+y4S0Ny+gvvw@mail.gmail.com>
Dne 25.5.2016 v 19:12 Kees Cook napsal(a):
> On Wed, May 25, 2016 at 3:46 AM, Michal Marek <mmarek@suse.com> wrote:
>> On 2016-05-24 19:04, Kees Cook wrote:
>>> On Mon, May 23, 2016 at 3:07 PM, Emese Revfy <re.emese@gmail.com> wrote:
>>>> This patch set introduce the GCC plugin infrastructure with examples for testing
>>>> and documentation.
>>>>
>>>> GCC plugins are loadable modules that provide extra features to the compiler.
>>>> They are useful for runtime instrumentation and static analysis.
>>>>
>>>> The infrastructure supports all gcc versions from 4.5 to 6.0, building
>>>> out-of-tree modules and building in a separate directory. Cross-compilation
>>>> is supported too but currently only the x86, arm, arm64 and uml architectures enable plugins.
>>>>
>>>> This infrastructure was ported from grsecurity/PaX. Based on work created by the PaX Team.
>>>> It is a CII project supported by the Linux Foundation.
>>>>
>>>> Emese Revfy (4):
>>>> Shared library support
>>>> GCC plugin infrastructure
>>>> Add Cyclomatic complexity plugin
>>>> Add sancov plugin
>>>
>>> Michal, once -rc1 is out, can you carry this for -next?
>>
>> Yes.
>
> Awesome! Please consider it:
>
> Acked-by: Kees Cook <keescook@chromium.org>
I applied the series to kbuild.git#kbuild now, sorry for the delay.
Michal
next prev parent reply other threads:[~2016-06-07 20:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 22:07 [PATCH v9 0/4] Introduce GCC plugin infrastructure Emese Revfy
2016-05-23 22:08 ` [PATCH v9 1/4] Shared library support Emese Revfy
2016-05-23 22:09 ` [PATCH v9 2/4] GCC plugin infrastructure Emese Revfy
2016-05-23 22:10 ` [PATCH v9 3/4] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-06-14 19:29 ` Laura Abbott
2016-06-14 22:33 ` Emese Revfy
2016-06-15 20:53 ` Emese Revfy
2016-06-15 22:41 ` Kees Cook
2016-05-23 22:11 ` [PATCH v9 4/4] Add sancov plugin Emese Revfy
2016-05-24 17:04 ` [PATCH v9 0/4] Introduce GCC plugin infrastructure Kees Cook
2016-05-25 10:46 ` Michal Marek
2016-05-25 17:12 ` Kees Cook
2016-06-07 20:58 ` Michal Marek [this message]
2016-06-07 20:59 ` Kees Cook
2016-06-07 21:59 ` Emese Revfy
2016-06-07 21:58 ` Kees Cook
2016-06-08 6:59 ` Michal Marek
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=57573559.1010607@suse.com \
--to=mmarek@suse.com \
--cc=david.brown@linaro.org \
--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=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;
as well as URLs for NNTP newsgroup(s).