From: James Morris <jmorris@namei.org>
To: Kees Cook <keescook@chromium.org>
Cc: Tycho Andersen <tycho@tycho.ws>,
David Howells <dhowells@redhat.com>,
keyrings@vger.kernel.org,
linux-security-module <linux-security-module@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Eric Biggers <ebiggers3@gmail.com>
Subject: Re: [PATCH v3 1/3] big key: get rid of stack array allocation
Date: Thu, 10 May 2018 05:21:37 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1805100520100.12749@namei.org> (raw)
In-Reply-To: <alpine.LRH.2.21.1805100519200.12749@namei.org>
On Thu, 10 May 2018, James Morris wrote:
> >
> > Reviewed-by: Kees Cook <keescook@chromium.org>
> >
> > James, are these something you can take into your tree?
>
> Sure!
Although, normally, these would likely come in to mine via David's tree.
Please do that unless there's a special case here.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2018-05-09 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 20:26 Tycho Andersen
2018-04-24 20:26 ` [PATCH v3 2/3] dh key: get rid of stack allocated array Tycho Andersen
2018-04-24 20:26 ` [PATCH v3 3/3] dh key: get rid of stack allocated array for zeroes Tycho Andersen
2018-05-04 13:42 ` [PATCH v3 1/3] big key: get rid of stack array allocation Tycho Andersen
2018-05-08 23:14 ` Kees Cook
2018-05-09 19:19 ` James Morris
2018-05-09 19:21 ` James Morris [this message]
2018-05-09 19:50 ` Kees Cook
2018-05-11 20:09 ` James Morris
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=alpine.LRH.2.21.1805100520100.12749@namei.org \
--to=jmorris@namei.org \
--cc=Jason@zx2c4.com \
--cc=dhowells@redhat.com \
--cc=ebiggers3@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=tycho@tycho.ws \
/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
all inboxes | Powered by JetHome®