From: Kees Cook <keescook@chromium.org>
To: Emese Revfy <re.emese@gmail.com>
Cc: Michal Marek <mmarek@suse.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 14:58:27 -0700 [thread overview]
Message-ID: <CAGXu5jLGCCoM83wXXasVz=1neBKbfZmrcrT39ZXqXTh7FUgEaA@mail.gmail.com> (raw)
In-Reply-To: <20160607235935.60ef8505b54f052a464bc4de@gmail.com>
On Tue, Jun 7, 2016 at 2:59 PM, Emese Revfy <re.emese@gmail.com> wrote:
> On Tue, 7 Jun 2016 13:59:53 -0700
> Kees Cook <keescook@chromium.org> wrote:
>
>> >
>> > I applied the series to kbuild.git#kbuild now, sorry for the delay.
>>
>> Awesome! Thank you very much. I'll prepare the latent entropy plugin
>> for -next now too.
>
> I'll send a new patch series this week because I'm developing a small feature and
> I'm fixing the handling of tail calls.
Depending on timing, it may be best to send a delta patch from
kbuild.git#kbuild. I assume that would be easier for Michal to carry.
-Kees
--
Kees Cook
Chrome OS & Brillo Security
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Emese Revfy <re.emese@gmail.com>
Cc: Michal Marek <mmarek@suse.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: [kernel-hardening] Re: [PATCH v9 0/4] Introduce GCC plugin infrastructure
Date: Tue, 7 Jun 2016 14:58:27 -0700 [thread overview]
Message-ID: <CAGXu5jLGCCoM83wXXasVz=1neBKbfZmrcrT39ZXqXTh7FUgEaA@mail.gmail.com> (raw)
In-Reply-To: <20160607235935.60ef8505b54f052a464bc4de@gmail.com>
On Tue, Jun 7, 2016 at 2:59 PM, Emese Revfy <re.emese@gmail.com> wrote:
> On Tue, 7 Jun 2016 13:59:53 -0700
> Kees Cook <keescook@chromium.org> wrote:
>
>> >
>> > I applied the series to kbuild.git#kbuild now, sorry for the delay.
>>
>> Awesome! Thank you very much. I'll prepare the latent entropy plugin
>> for -next now too.
>
> I'll send a new patch series this week because I'm developing a small feature and
> I'm fixing the handling of tail calls.
Depending on timing, it may be best to send a delta patch from
kbuild.git#kbuild. I assume that would be easier for Michal to carry.
-Kees
--
Kees Cook
Chrome OS & Brillo Security
next prev parent reply other threads:[~2016-06-07 21:58 UTC|newest]
Thread overview: 43+ 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:07 ` [kernel-hardening] " Emese Revfy
2016-05-23 22:08 ` [PATCH v9 1/4] Shared library support Emese Revfy
2016-05-23 22:08 ` [kernel-hardening] " Emese Revfy
2016-05-23 22:09 ` [PATCH v9 2/4] GCC plugin infrastructure Emese Revfy
2016-05-23 22:09 ` [kernel-hardening] " Emese Revfy
2016-05-23 22:10 ` [PATCH v9 3/4] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-05-23 22:10 ` [kernel-hardening] " Emese Revfy
2016-06-14 19:29 ` Laura Abbott
2016-06-14 19:29 ` [kernel-hardening] " Laura Abbott
2016-06-14 22:33 ` Emese Revfy
2016-06-14 22:33 ` [kernel-hardening] " Emese Revfy
2016-06-15 20:53 ` Emese Revfy
2016-06-15 20:53 ` [kernel-hardening] " Emese Revfy
2016-06-15 22:41 ` Kees Cook
2016-06-15 22:41 ` [kernel-hardening] " Kees Cook
2016-06-15 22:41 ` Kees Cook
2016-05-23 22:11 ` [PATCH v9 4/4] Add sancov plugin Emese Revfy
2016-05-23 22:11 ` [kernel-hardening] " Emese Revfy
2016-05-24 17:04 ` [PATCH v9 0/4] Introduce GCC plugin infrastructure Kees Cook
2016-05-24 17:04 ` [kernel-hardening] " Kees Cook
2016-05-24 17:04 ` Kees Cook
2016-05-25 10:46 ` Michal Marek
2016-05-25 10:46 ` [kernel-hardening] " Michal Marek
2016-05-25 10:46 ` Michal Marek
2016-05-25 17:12 ` Kees Cook
2016-05-25 17:12 ` [kernel-hardening] " Kees Cook
2016-05-25 17:12 ` Kees Cook
2016-06-07 20:58 ` Michal Marek
2016-06-07 20:58 ` [kernel-hardening] " Michal Marek
2016-06-07 20:58 ` Michal Marek
2016-06-07 20:59 ` Kees Cook
2016-06-07 20:59 ` [kernel-hardening] " Kees Cook
2016-06-07 20:59 ` Kees Cook
2016-06-07 21:59 ` Emese Revfy
2016-06-07 21:59 ` [kernel-hardening] " Emese Revfy
2016-06-07 21:59 ` Emese Revfy
2016-06-07 21:58 ` Kees Cook [this message]
2016-06-07 21:58 ` [kernel-hardening] " Kees Cook
2016-06-07 21:58 ` Kees Cook
2016-06-08 6:59 ` Michal Marek
2016-06-08 6:59 ` [kernel-hardening] " Michal Marek
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='CAGXu5jLGCCoM83wXXasVz=1neBKbfZmrcrT39ZXqXTh7FUgEaA@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=david.brown@linaro.org \
--cc=dvyukov@google.com \
--cc=fengguang.wu@intel.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--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 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.