From: Mark Salyzyn <salyzyn@android.com>
To: linux-kernel@vger.kernel.org
Cc: kevin.brodsky@arm.com, catalin.marinas@arm.com,
will.deacon@arm.com, mingo@kernel.org, borntraeger@de.ibm.com,
james.morse@arm.com, peterz@infradead.org, Dave.Martin@arm.com,
credmonster@gmail.com, zijun_hu@htc.com, mark.rutland@arm.com,
jszhang@marvell.com, labbott@redhat.com, john.stultz@linaro.org,
keescook@chromium.org, linux-arm-kernel@lists.infradead.org,
takahiro.akashi@linaro.org, mmarek@suse.com,
ard.biesheuvel@linaro.org, Mark Salyzyn <salyzyn@android.com>
Subject: [PATCH v3 0/3] arm64: Add CONFIG_KUSER_HELPERS
Date: Mon, 11 Sep 2017 08:26:27 -0700 [thread overview]
Message-ID: <20170911152635.95367-1-salyzyn@android.com> (raw)
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)
next reply other threads:[~2017-09-11 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 15:26 Mark Salyzyn [this message]
2017-09-19 22:02 ` [PATCH v3 0/3] arm64: Add CONFIG_KUSER_HELPERS Kees Cook
2017-09-20 9:15 ` Will Deacon
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=20170911152635.95367-1-salyzyn@android.com \
--to=salyzyn@android.com \
--cc=Dave.Martin@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=borntraeger@de.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=credmonster@gmail.com \
--cc=james.morse@arm.com \
--cc=john.stultz@linaro.org \
--cc=jszhang@marvell.com \
--cc=keescook@chromium.org \
--cc=kevin.brodsky@arm.com \
--cc=labbott@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mmarek@suse.com \
--cc=peterz@infradead.org \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.com \
--cc=zijun_hu@htc.com \
/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