public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: James Morris <jmorris@namei.org>,
	John Johansen <john.johansen@canonical.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, Kees Cook <kees@outflux.net>,
	Paul Moore <paul@paul-moore.com>,
	LSM <linux-security-module@vger.kernel.org>,
	James Morris <james.l.morris@oracle.com>,
	linux-kernel@vger.kernel.org,
	Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: Module stacking next steps
Date: Thu, 30 Apr 2015 08:10:30 -0700	[thread overview]
Message-ID: <554245E6.9000004@schaufler-ca.com> (raw)
In-Reply-To: <554240D9.506@schaufler-ca.com>

On 4/30/2015 7:48 AM, Casey Schaufler wrote:
> On 4/30/2015 4:20 AM, James Morris wrote:
>> On Wed, 29 Apr 2015, John Johansen wrote:
>>
>>> 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, ...)
>> Ok, Casey, please send an updated final version for everyone to check.
> Are you planning to update security-next soon? I think that it will
> be easier for everyone if I base it on the 4.1-rc than the 4.0-rc.
> Alternatively, I could base it on 4.0. I can do any of 'em, but I'd
> hate to have to do it more often than I have to.

Whoops! I read mail addressed directly to me before I read what goes
just to lists. I see that security-next is updated. I will have the update
ready as quickly as possible. Thank you.


      reply	other threads:[~2015-04-30 15:10 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
2015-04-30 11:20     ` James Morris
2015-04-30 14:48       ` Casey Schaufler
2015-04-30 15:10         ` Casey Schaufler [this message]

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=554245E6.9000004@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=james.l.morris@oracle.com \
    --cc=jmorris@namei.org \
    --cc=john.johansen@canonical.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox