From: John Johansen <john.johansen@canonical.com>
To: James Morris <jmorris@namei.org>,
Casey Schaufler <casey@schaufler-ca.com>,
Stephen Smalley <sds@tycho.nsa.gov>, Kees Cook <kees@outflux.net>,
Paul Moore <paul@paul-moore.com>
Cc: LSM <linux-security-module@vger.kernel.org>,
James Morris <james.l.morris@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: Module stacking next steps
Date: Wed, 29 Apr 2015 19:45:11 -0700 [thread overview]
Message-ID: <55419737.4000907@canonical.com> (raw)
In-Reply-To: <alpine.LRH.2.11.1504301138120.10370@namei.org>
On 04/29/2015 06:55 PM, James Morris wrote:
> On Tue, 21 Apr 2015, Casey Schaufler wrote:
>
>>
>> James, do you want to take the module stacking changes in through
>> the security tree? Are there remaining objections or concerns? What
>> procedure would you like to follow?
>
> What's the overall consensus on this -- do people generally see it as
> useful and necessary, and is it ready to go in?
>
> Any objections or concerns?
>
No objections, and I know there are several people interested in seeing
this land.
I am happy with the code, and my only concerns lie with things that this
explicitly doesn't support yet (ie. larger lsm stacking, secids, ...)
next prev parent reply other threads:[~2015-04-30 2:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5536F260.3080201@schaufler-ca.com>
2015-04-30 1:55 ` Module stacking next steps James Morris
2015-04-30 2:02 ` Kees Cook
2015-04-30 2:45 ` John Johansen [this message]
2015-04-30 11:20 ` James Morris
2015-04-30 14:48 ` Casey Schaufler
2015-04-30 15:10 ` Casey Schaufler
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=55419737.4000907@canonical.com \
--to=john.johansen@canonical.com \
--cc=casey@schaufler-ca.com \
--cc=james.l.morris@oracle.com \
--cc=jmorris@namei.org \
--cc=kees@outflux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
/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.