[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 21 Feb 2019 14:48:19 +0000
From: Mark Rutland <mark.rutland@....com>
To: Christophe Leroy <christophe.leroy@....fr>
Cc: Russell Currey <ruscur@...sell.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, 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/
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.
