[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.21.2006160403190.9951@namei.org>
Date: Tue, 16 Jun 2020 04:03:33 +1000 (AEST)
From: James Morris <jmorris@...ei.org>
To: Micah Morton <mortonm@...omium.org>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>,
Paul Moore <paul@...l-moore.com>,
Casey Schaufler <casey@...aufler-ca.com>,
John Johansen <john.johansen@...onical.com>
Subject: Re: [GIT PULL] SafeSetID LSM changes for v5.8
On Mon, 15 Jun 2020, Micah Morton wrote:
> On Sun, Jun 14, 2020 at 10:21 PM James Morris <jmorris@...ei.org> wrote:
> >
> > On Sun, 14 Jun 2020, Micah Morton wrote:
> >
> > > This patch was sent to the security mailing list and there were no objections.
> >
> > Standard practice for new or modified LSM hooks is that they are reviewed
> > and acked by maintainers of major LSMs (SELinux, AppArmor, and Smack, at
> > least).
> >
> > "No objections" should be considered "not reviewed".
> >
> > Can you add your tree to linux-next?
> > https://www.kernel.org/doc/man-pages/linux-next.html
>
> Sure, I can do that. I should just send an email to Stephen Rothwell
> asking him to include the -next branch from my tree?
Yep, thanks.
>
> >
> > --
> > James Morris
> > <jmorris@...ei.org>
> >
>
--
James Morris
<jmorris@...ei.org>
Powered by blists - more mailing lists