From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] arm64: kernel: Add support for User Access Override
Date: Fri, 05 Feb 2016 16:40:54 +0100 [thread overview]
Message-ID: <13475776.5b1DTHhHh9@wuerfel> (raw)
In-Reply-To: <1454684330-892-1-git-send-email-james.morse@arm.com>
On Friday 05 February 2016 14:58:45 James Morse wrote:
> This series adds support for User Access Override (UAO; part of the ARMv8.2
> Extensions[0]). When enabled, this causes the get_user() accessors to use
> the unprivileged load/store instructions. When addr_limit is set to
> KERNEL_DS, we set the override bit allowing privileged access.
>
> Because the unprivileged instructions don't trip PAN, the last patch changes
> which 'alternative' values are swapped in, allowing PAN to be left enabled
> during get_user() and friends.
>
> This series can be retrieved from:
> git://linux-arm.org/linux-jm.git -b uao/v2
>
Looks very nice. I have no complaints about the implementations, but two questions:
* There was recently some work in reducing the number of set_fs() calls in
the compat_ioctl, which further reduces the attack surface. Should we try to
continue that effort in other syscalls?
* Do we expect to handle this using live patching indefinitely? I can imagine
that at some point in the future, ARMv8.2+ systems will be the vast majority,
so it might be nice to support enabling it unconditionally (same for any
of the alternative bits really). Is there a long-term strategy?
Arnd
next prev parent reply other threads:[~2016-02-05 15:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 14:58 [PATCH v2 0/5] arm64: kernel: Add support for User Access Override James Morse
2016-02-05 14:58 ` [PATCH v2 1/5] arm64: cpufeature: Change read_cpuid() to use sysreg's mrs_s macro James Morse
2016-02-05 14:58 ` [PATCH v2 2/5] arm64: add ARMv8.2 id_aa64mmfr2 boiler plate James Morse
2016-03-03 17:59 ` Christopher Covington
2016-03-03 18:27 ` Robin Murphy
2016-03-03 19:03 ` Christopher Covington
2016-03-03 19:19 ` Will Deacon
2016-03-04 10:20 ` Suzuki K. Poulose
2016-03-04 13:37 ` James Morse
2016-03-04 13:54 ` Robin Murphy
2016-03-04 14:59 ` Mark Rutland
2016-03-04 18:15 ` Christopher Covington
2016-02-05 14:58 ` [PATCH v2 3/5] arm64: kernel: Add support for User Access Override James Morse
2016-02-18 12:26 ` Catalin Marinas
2016-02-05 14:58 ` [PATCH v2 4/5] arm64: cpufeature: Test 'matches' pointer to find the end of the list James Morse
2016-02-05 14:58 ` [PATCH v2 5/5] arm64: kernel: Don't toggle PAN on systems with UAO James Morse
2016-02-18 14:36 ` Catalin Marinas
2016-02-18 14:43 ` James Morse
2016-02-05 15:40 ` Arnd Bergmann [this message]
2016-02-09 9:47 ` [PATCH v2 0/5] arm64: kernel: Add support for User Access Override Will Deacon
2016-02-18 18:03 ` Catalin Marinas
2016-02-19 15:38 ` Peter Maydell
2016-02-19 16:46 ` Catalin Marinas
2016-02-19 16:54 ` Peter Maydell
2016-02-19 16:57 ` Ard Biesheuvel
2016-02-19 17:03 ` Peter Maydell
2016-03-07 16:43 ` James Morse
2016-03-07 17:23 ` Russell King - ARM Linux
2016-03-07 17:40 ` James Morse
2016-03-07 17:51 ` Russell King - ARM Linux
2016-03-07 17:38 ` Catalin Marinas
2016-03-07 20:54 ` Kees Cook
2016-03-08 17:19 ` Catalin Marinas
2016-03-08 17:39 ` Kees Cook
2016-03-08 18:22 ` Catalin Marinas
2016-03-08 18:27 ` Kees Cook
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=13475776.5b1DTHhHh9@wuerfel \
--to=arnd@arndb.de \
--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