From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752558AbbD3OtB (ORCPT ); Thu, 30 Apr 2015 10:49:01 -0400 Received: from smtp106.biz.mail.bf1.yahoo.com ([98.139.244.54]:37266 "EHLO smtp106.biz.mail.bf1.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751547AbbD3Os6 (ORCPT ); Thu, 30 Apr 2015 10:48:58 -0400 X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 1hTJVegVM1nCl0Hw3VbDhQuhEieviPuiE4jFjlqyyHSfPLk dMo8Dd.QVcefoItteP91IaOMtEArvrDHZJNgz3fOYiJvQrztaJ3X9SMxosCe DdRuf95CjrvdC.DHL0JKPX5anoG7tBb_tyg1TxwLTyrjzTcX.c8uwns9jdZW Q6LICdst7Mts1nv_jgisfLPKJG.PI7Dy9mc2PDQFd_O5W30gbmJDOq4UBsx9 SZxod5fPYsYe7F0kk15pEztkhxZSHP2zrNoBfvWfD8s8UR6VfixO20Ub_sGL c68_gK6sPDQI9nT8qXYeSjMcETKQG2pnpZIf3f4MrAJKkCKZa9ILS3s19mRG 2f0gFYE9F5yafzi.a05fv5qM58JvfMOaOciWtR9EexYPb1rPOtWQ6Gc1oUB3 j2LIf11XGZp2O779nTZ.69X9_TWajNQVkodvgWCsvwkO_aHcqjhDEyDLxrvG HpKvdliswV7mO4VX0xLBWasup99KAtKs4gq6R2Kir9uFoAzWJ6JlLCr0e6fk 7tMan8CtlveeibJgtARrSqpzxASK1fPiNj.LoYRnqGw-- X-Yahoo-SMTP: OIJXglSswBDfgLtXluJ6wiAYv6_cnw-- Message-ID: <554240D9.506@schaufler-ca.com> Date: Thu, 30 Apr 2015 07:48:57 -0700 From: Casey Schaufler User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: James Morris , John Johansen CC: Stephen Smalley , Kees Cook , Paul Moore , LSM , James Morris , linux-kernel@vger.kernel.org, Casey Schaufler Subject: Re: Module stacking next steps References: <5536F260.3080201@schaufler-ca.com> <55419737.4000907@canonical.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.