Security updates for v4.15 and beyond
casey at schaufler-ca.com
Wed Sep 27 00:18:50 UTC 2017
On 9/26/2017 5:03 PM, James Morris wrote:
> On Tue, 26 Sep 2017, John Johansen wrote:
>> I have to agree with Paul here, unless there are infrastructure
>> changes this feels like an extra hop. With next directly pulling
>> security (for infrastructure) and LSM changes merge conflicts will
>> show up there. At which point we are going to need to coordinate,
>> but these should be rare.
> Ok, it seems a consensus is emerging to go with Paul's idea of having
> larger, frequently updated LSMs merge directly to Linus. If Linus is okay
> with that (I'm assuing he will be), then that's how we'll do thing from
> Of course, any LSM or other security mechanism is still welcome to be
> merged via my tree.
Smack will stick with the security tree for the time being.
The amount of change is small (due to simplicity! :) ) and I
seriously doubt Linus wants to deal with the onesy-twosy patch
I will stick with the security tree for the stacking work as well.
Having SELinux and AppArmor going off on their own is a royal pain
for that, but there's already audit and networking to worry about
so it's hard to argue that life is going to be that much harder.
Oh well. I knew the job was dangerous when I took it.
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the Linux-security-module-archive