[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ee891ded467e1fd473c9b075658b959e091e8f6.camel@russell.cc>
Date: Fri, 22 Feb 2019 11:11:49 +1100
From: Russell Currey <ruscur@...sell.cc>
To: Mark Rutland <mark.rutland@....com>, Christophe Leroy
<christophe.leroy@....fr>
Cc: linuxppc-dev@...ts.ozlabs.org, mpe@...erman.id.au, npiggin@...il.com,
kernel-hardening@...ts.openwall.com
Subject: Re: [PATCH 3/7] powerpc/mm: Add a framework for Kernel Userspace
Access Protection
On Thu, 2019-02-21 at 14:48 +0000, Mark Rutland wrote:
> On Thu, Feb 21, 2019 at 11:46:06AM +0100, Christophe Leroy wrote:
> >
> > Le 21/02/2019 à 10:35, Russell Currey a écrit :
> > > From: Christophe Leroy <christophe.leroy@....fr>
> > >
> > > This patch implements a framework for Kernel Userspace Access
> > > Protection.
> > >
> > > Then subarches will have to possibility to provide their own
> > > implementation by providing setup_kuap() and
> > > lock/unlock_user_access()
> > >
> > > Some platform will need to know the area accessed and whether it
> > > is
> > > accessed from read, write or both. Therefore source, destination
> > > and
> > > size and handed over to the two functions.
> >
> > Should we also consider adding user_access_begin() and the 3 other
> > associated macros ?
> >
> > See x86 for details.
>
> As a heads-up, there are some potential issues with
> user_access_{begin,end}() that may affect PPC. There's a long thread
> starting at:
>
> https://lkml.kernel.org/r/1547560709-56207-4-git-send-email-julien.thierry@arm.com/
I'd say we should look at adding those macros, but as follow-up work
after this series (and after we know what's going on with those issues)
- Russell
>
> Thanks,
> Mark.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
