From: danielj@mellanox.com (Daniel Jurgens)
Date: Mon, 27 Jun 2016 13:40:21 +0000
Subject: [refpolicy] [PATCH 1/1] flask: Add classes and SIDs for
 InfiniBand support
References: <1466711268-61413-1-git-send-email-danielj@mellanox.com>
	<1466711268-61413-2-git-send-email-danielj@mellanox.com>
	<b93cedb4-6330-f588-1f2d-8c8ccfac1fdc@ieee.org>
Message-ID: <DB6PR0501MB2261132D4A1CC3A8830E9CDAC4210@DB6PR0501MB2261.eurprd05.prod.outlook.com>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

On 6/25/2016 12:02 PM, Chris PeBenito wrote:
> On 06/23/16 15:47, Dan Jurgens wrote:
>> From: Daniel Jurgens <danielj@mellanox.com>
>>
>> Add new classes, access vectors, SIDs required for SELinux to provide
>> access control for InfiniBand.  Add stub policy so refpolicy still
>> compiles.  Useful policy will be added after the SELinux kernel and
>> userspace changes are in place.
> 
> This will have to wait until the corresponding code changes start making
> their way upstream.  I don't want to merge any new classes, and even
> more so, initial SIDs, until I'm confident it won't be changing.

Sure, I will resubmit after the kernel changes are accepted upstream.

> 
> I'm not sure that a new infiniband module makes sense.  I could see it
> going in corenetwork.
> 

I can move it there when I do resubmit.