From: Kees Cook <keescook@chromium.org>
To: James Morris <jmorris@namei.org>
Cc: "Mickaël Salaün" <mic@digikod.net>,
LKML <linux-kernel@vger.kernel.org>,
"Mimi Zohar" <zohar@linux.vnet.ibm.com>,
"Luis R . Rodriguez" <mcgrof@kernel.org>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"# 3.4.x" <stable@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH v1] module: Fully remove the kernel_module_from_file hook
Date: Thu, 28 Jul 2016 11:30:39 -0700 [thread overview]
Message-ID: <CAGXu5jKt-td0atFEPFtVYCob1n-V+VeKG6hxv4CsDEiAMktgzw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1607122248350.10974@namei.org>
On Tue, Jul 12, 2016 at 5:48 AM, James Morris <jmorris@namei.org> wrote:
> On Sat, 9 Jul 2016, Mickaël Salaün wrote:
>
>> Fixes: a1db74209483 ("module: replace copy_module_from_fd with kernel version")
>>
>> Signed-off-by: Mickaël Salaün <mic@digikod.net>
>> Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>
>> Cc: Kees Cook <keescook@chromium.org>
>> Cc: Luis R. Rodriguez <mcgrof@kernel.org>
>> Cc: Rusty Russell <rusty@rustcorp.com.au>
>> Cc: Linus Torvalds <torvalds@linux-foundation.org>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
>
> Acked-by: James Morris <james.l.morris@oracle.com>
James, can you take this via the security-next tree?
Thanks!
-Kees
--
Kees Cook
Chrome OS & Brillo Security
next prev parent reply other threads:[~2016-07-28 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 18:19 [PATCH v1] module: Fully remove the kernel_module_from_file hook Mickaël Salaün
2016-07-11 18:41 ` Kees Cook
2016-07-11 21:42 ` Greg Kroah-Hartman
2016-07-12 12:48 ` James Morris
2016-07-28 18:30 ` Kees Cook [this message]
2016-08-01 2:34 ` Mimi Zohar
2016-08-02 1:12 ` 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=CAGXu5jKt-td0atFEPFtVYCob1n-V+VeKG6hxv4CsDEiAMktgzw@mail.gmail.com \
--to=keescook@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mic@digikod.net \
--cc=rusty@rustcorp.com.au \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zohar@linux.vnet.ibm.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).