From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] Mitigations against spectre-v1 in the arm64 Linux kernel
Date: Mon, 5 Feb 2018 15:34:15 +0000 [thread overview]
Message-ID: <1517844864-15887-1-git-send-email-will.deacon@arm.com> (raw)
Hi all,
This series implements some mitigations against spectre-v1 for arm64. It
broadly follows the work that has been done for x86, by implementing:
* A back-end version of array_index_mask_nospec() to suppress any
compiler optimisations that could introduce unwanted speculative
paths
* Masking of the syscall number to restrict speculation through the
syscall table
* Masking of __user pointers prior to deference in uaccess routines
The latter introduces complications in access_ok and set_fs which are
also handled in this series.
Cheers,
Will
--->8
Robin Murphy (3):
arm64: Implement array_index_mask_nospec()
arm64: Make USER_DS an inclusive limit
arm64: Use pointer masking to limit uaccess speculation
Will Deacon (6):
arm64: barrier: Add CSDB macros to control data-value prediction
arm64: entry: Ensure branch through syscall table is bounded under
speculation
arm64: uaccess: Prevent speculative use of the current addr_limit
arm64: uaccess: Don't bother eliding access_ok checks in
__{get,put}_user
arm64: uaccess: Mask __user pointers for __arch_{clear,copy_*}_user
arm64: futex: Mask __user pointers prior to dereference
arch/arm64/include/asm/assembler.h | 18 +++++
arch/arm64/include/asm/barrier.h | 22 ++++++
arch/arm64/include/asm/futex.h | 9 ++-
arch/arm64/include/asm/processor.h | 3 +
arch/arm64/include/asm/uaccess.h | 155 +++++++++++++++++++++++++------------
arch/arm64/kernel/arm64ksyms.c | 4 +-
arch/arm64/kernel/entry.S | 6 +-
arch/arm64/lib/clear_user.S | 6 +-
arch/arm64/lib/copy_in_user.S | 5 +-
arch/arm64/mm/fault.c | 4 +-
10 files changed, 170 insertions(+), 62 deletions(-)
--
2.1.4
next reply other threads:[~2018-02-05 15:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 15:34 Will Deacon [this message]
2018-02-05 15:34 ` [PATCH 1/9] arm64: barrier: Add CSDB macros to control data-value prediction Will Deacon
2018-02-05 15:34 ` [PATCH 2/9] arm64: Implement array_index_mask_nospec() Will Deacon
2018-02-05 15:34 ` [PATCH 3/9] arm64: Make USER_DS an inclusive limit Will Deacon
2018-02-05 15:34 ` [PATCH 4/9] arm64: Use pointer masking to limit uaccess speculation Will Deacon
2018-02-05 15:34 ` [PATCH 5/9] arm64: entry: Ensure branch through syscall table is bounded under speculation Will Deacon
2018-02-05 15:34 ` [PATCH 6/9] arm64: uaccess: Prevent speculative use of the current addr_limit Will Deacon
2018-02-05 15:34 ` [PATCH 7/9] arm64: uaccess: Don't bother eliding access_ok checks in __{get, put}_user Will Deacon
2018-02-05 15:34 ` [PATCH 8/9] arm64: uaccess: Mask __user pointers for __arch_{clear, copy_*}_user Will Deacon
2018-02-05 15:34 ` [PATCH 9/9] arm64: futex: Mask __user pointers prior to dereference Will Deacon
2018-02-06 22:17 ` [PATCH 0/9] Mitigations against spectre-v1 in the arm64 Linux kernel Catalin Marinas
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=1517844864-15887-1-git-send-email-will.deacon@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).