From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] arm64: Add CONFIG_KUSER_HELPERS
Date: Wed, 20 Sep 2017 10:15:56 +0100 [thread overview]
Message-ID: <20170920091555.GA3782@arm.com> (raw)
In-Reply-To: <CAGXu5jK-i_Eqfm1mZ-Kz5dqsKuCt_-MDymkb735VXCV9aOnvwQ@mail.gmail.com>
On Tue, Sep 19, 2017 at 03:02:22PM -0700, Kees Cook wrote:
> On Mon, Sep 11, 2017 at 8:26 AM, Mark Salyzyn <salyzyn@android.com> wrote:
> > Make it possible to disable the kuser helpers by adding a KUSER_HELPERS
> > config option (enabled by default). When disabled, all kuser
> > helpers-related code is removed from the kernel and no mapping is done
> > at the fixed high address (0xffff0000); any attempt to use a kuser
> > helper from a 32-bit process will result in a segfault.
> >
> > Signed-off-by: Mark Salyzyn <salyzyn@android.com>
> >
> > v2:
> > - vectors_page and compat_vdso_spec as array of 2
> > - free sigpage if vectors allocation failed
> > - adjust makefile so one line for each of the assembler source modules
> > - split off assembler changes to a new previous patch in series to reduce churn
> > - modify slightly the feature documentation to reduce its reach
> > - modify slightly the feature documentation to rationalize the yes default.
> > - There are more ifdefs as a result of the rebase.
> >
> > v3:
> > - rebase (minor conflicts)
>
> This looks great to me. I'd love to see kuser helpers gone. :)
>
> Catalin, Will, does this need anything else?
I haven't had chance to look at the patches yet (buried in other stuff), but
I aim to get to it in the next couple of weeks.
Will
next prev parent reply other threads:[~2017-09-20 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 15:26 [PATCH v3 0/3] arm64: Add CONFIG_KUSER_HELPERS Mark Salyzyn
2017-09-19 22:02 ` Kees Cook
2017-09-20 9:15 ` Will Deacon [this message]
2017-10-31 18:42 ` Mark Salyzyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170920091555.GA3782@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).