From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Kees Cook <keescook@chromium.org>
Cc: "James Morris" <jmorris@namei.org>,
"Mickaël Salaün" <mic@digikod.net>,
LKML <linux-kernel@vger.kernel.org>,
"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: Sun, 31 Jul 2016 22:34:43 -0400 [thread overview]
Message-ID: <1470018883.23563.373.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAGXu5jKt-td0atFEPFtVYCob1n-V+VeKG6hxv4CsDEiAMktgzw@mail.gmail.com>
On Do, 2016-07-28 at 11:30 -0700, Kees Cook wrote:
> 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?
Kees, thank you for staying on top of this. James, did you want a pull
request for this patch?
Mimi
next prev parent reply other threads:[~2016-08-01 2:35 UTC|newest]
Thread overview: 8+ 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-11 21:42 ` Greg Kroah-Hartman
2016-07-12 12:48 ` James Morris
2016-07-28 18:30 ` Kees Cook
2016-08-01 2:34 ` Mimi Zohar [this message]
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=1470018883.23563.373.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jmorris@namei.org \
--cc=keescook@chromium.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 \
/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.