[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhSSZzDeM1bcOjVBN6u5KPAvMysg3sLcSniq+cLr65WFqg@mail.gmail.com>
Date: Thu, 27 May 2021 10:18:52 -0400
From: Paul Moore <paul@...l-moore.com>
To: James Morris <jmorris@...ei.org>
Cc: Ondrej Mosnacek <omosnace@...hat.com>,
Michael Ellerman <mpe@...erman.id.au>,
Linux Security Module list
<linux-security-module@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>,
Stephen Smalley <stephen.smalley.work@...il.com>,
SElinux list <selinux@...r.kernel.org>,
linuxppc-dev@...ts.ozlabs.org,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
bpf <bpf@...r.kernel.org>, network dev <netdev@...r.kernel.org>,
Linux kernel mailing list <linux-kernel@...r.kernel.org>,
Casey Schaufler <casey@...aufler-ca.com>
Subject: Re: [PATCH v2] lockdown,selinux: avoid bogus SELinux lockdown
permission checks
On Thu, May 27, 2021 at 12:33 AM James Morris <jmorris@...ei.org> wrote:
> On Wed, 26 May 2021, Ondrej Mosnacek wrote:
>
> > Thanks, Michael!
> >
> > James/Paul, is there anything blocking this patch from being merged?
> > Especially the BPF case is causing real trouble for people and the
> > only workaround is to broadly allow lockdown::confidentiality in the
> > policy.
>
> It would be good to see more signoffs/reviews, especially from Paul, but
> he is busy with the io_uring stuff.
Yes, it's been a busy week with various things going on around here.
I looked at the v1 posting but haven't had a chance yet to look at v2;
I promise to get to it today, but it might not happen until later
tonight.
> Let's see if anyone else can look at this in the next couple of days.
--
paul moore
www.paul-moore.com
Powered by blists - more mailing lists