From: ebiederm@xmission.com (Eric W. Biederman)
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
linux-arch@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Alan Cox <alan.cox@intel.com>,
x86@kernel.org, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
kernel-hardening@lists.openwall.com, tglx@linutronix.de,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
Elena Reshetova <elena.reshetova@intel.com>,
alan@linux.intel.com
Subject: [kernel-hardening] Re: [PATCH v2 04/19] x86: implement ifence()
Date: Thu, 11 Jan 2018 20:27:45 -0600 [thread overview]
Message-ID: <87efmv4xr2.fsf@xmission.com> (raw)
In-Reply-To: <151571800589.27429.13615996439124092232.stgit@dwillia2-desk3.amr.corp.intel.com> (Dan Williams's message of "Thu, 11 Jan 2018 16:46:45 -0800")
Dan Williams <dan.j.williams@intel.com> writes:
> The new barrier, 'ifence', ensures that no instructions past the
> boundary are speculatively executed.
This needs a much better description.
If that description was valid we could add ifence in the syscall
entry path and not have any speculative execution to worry about in the
kernel.
Perhaps:
'ifence', ensures that no speculative execution that reaches the 'ifence'
boundary continues past the 'ifence' boundary.
> Previously the kernel only needed this fence in 'rdtsc_ordered', but it
> can also be used as a mitigation against Spectre variant1 attacks that
> speculative access memory past an array bounds check.
>
> 'ifence', via 'ifence_array_ptr', is an opt-in fallback to the default
> mitigation provided by '__array_ptr'. It is also proposed for blocking
> speculation in the 'get_user' path to bypass 'access_ok' checks. For
> now, just provide the common definition for later patches to build
> upon.
This part of the description is probably unnecessary.
Eric
>
> Suggested-by: Peter Zijlstra <peterz@infradead.org>
> Suggested-by: Alan Cox <alan.cox@intel.com>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Greg KH <gregkh@linuxfoundation.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: x86@kernel.org
> Signed-off-by: Elena Reshetova <elena.reshetova@intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> arch/x86/include/asm/barrier.h | 4 ++++
> arch/x86/include/asm/msr.h | 3 +--
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/include/asm/barrier.h b/arch/x86/include/asm/barrier.h
> index 7fb336210e1b..b04f572d6d97 100644
> --- a/arch/x86/include/asm/barrier.h
> +++ b/arch/x86/include/asm/barrier.h
> @@ -24,6 +24,10 @@
> #define wmb() asm volatile("sfence" ::: "memory")
> #endif
>
> +/* prevent speculative execution past this barrier */
> +#define ifence() alternative_2("", "mfence", X86_FEATURE_MFENCE_RDTSC, \
> + "lfence", X86_FEATURE_LFENCE_RDTSC)
> +
> #ifdef CONFIG_X86_PPRO_FENCE
> #define dma_rmb() rmb()
> #else
> diff --git a/arch/x86/include/asm/msr.h b/arch/x86/include/asm/msr.h
> index 07962f5f6fba..e426d2a33ff3 100644
> --- a/arch/x86/include/asm/msr.h
> +++ b/arch/x86/include/asm/msr.h
> @@ -214,8 +214,7 @@ static __always_inline unsigned long long rdtsc_ordered(void)
> * that some other imaginary CPU is updating continuously with a
> * time stamp.
> */
> - alternative_2("", "mfence", X86_FEATURE_MFENCE_RDTSC,
> - "lfence", X86_FEATURE_LFENCE_RDTSC);
> + ifence();
> return rdtsc();
> }
>
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
linux-arch@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Alan Cox <alan.cox@intel.com>,
x86@kernel.org, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
kernel-hardening@lists.openwall.com, tglx@linutronix.de,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
Elena Reshetova <elena.reshetova@intel.com>,
alan@linux.intel.com
Subject: Re: [PATCH v2 04/19] x86: implement ifence()
Date: Thu, 11 Jan 2018 20:27:45 -0600 [thread overview]
Message-ID: <87efmv4xr2.fsf@xmission.com> (raw)
In-Reply-To: <151571800589.27429.13615996439124092232.stgit@dwillia2-desk3.amr.corp.intel.com> (Dan Williams's message of "Thu, 11 Jan 2018 16:46:45 -0800")
Dan Williams <dan.j.williams@intel.com> writes:
> The new barrier, 'ifence', ensures that no instructions past the
> boundary are speculatively executed.
This needs a much better description.
If that description was valid we could add ifence in the syscall
entry path and not have any speculative execution to worry about in the
kernel.
Perhaps:
'ifence', ensures that no speculative execution that reaches the 'ifence'
boundary continues past the 'ifence' boundary.
> Previously the kernel only needed this fence in 'rdtsc_ordered', but it
> can also be used as a mitigation against Spectre variant1 attacks that
> speculative access memory past an array bounds check.
>
> 'ifence', via 'ifence_array_ptr', is an opt-in fallback to the default
> mitigation provided by '__array_ptr'. It is also proposed for blocking
> speculation in the 'get_user' path to bypass 'access_ok' checks. For
> now, just provide the common definition for later patches to build
> upon.
This part of the description is probably unnecessary.
Eric
>
> Suggested-by: Peter Zijlstra <peterz@infradead.org>
> Suggested-by: Alan Cox <alan.cox@intel.com>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Greg KH <gregkh@linuxfoundation.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: x86@kernel.org
> Signed-off-by: Elena Reshetova <elena.reshetova@intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> arch/x86/include/asm/barrier.h | 4 ++++
> arch/x86/include/asm/msr.h | 3 +--
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/include/asm/barrier.h b/arch/x86/include/asm/barrier.h
> index 7fb336210e1b..b04f572d6d97 100644
> --- a/arch/x86/include/asm/barrier.h
> +++ b/arch/x86/include/asm/barrier.h
> @@ -24,6 +24,10 @@
> #define wmb() asm volatile("sfence" ::: "memory")
> #endif
>
> +/* prevent speculative execution past this barrier */
> +#define ifence() alternative_2("", "mfence", X86_FEATURE_MFENCE_RDTSC, \
> + "lfence", X86_FEATURE_LFENCE_RDTSC)
> +
> #ifdef CONFIG_X86_PPRO_FENCE
> #define dma_rmb() rmb()
> #else
> diff --git a/arch/x86/include/asm/msr.h b/arch/x86/include/asm/msr.h
> index 07962f5f6fba..e426d2a33ff3 100644
> --- a/arch/x86/include/asm/msr.h
> +++ b/arch/x86/include/asm/msr.h
> @@ -214,8 +214,7 @@ static __always_inline unsigned long long rdtsc_ordered(void)
> * that some other imaginary CPU is updating continuously with a
> * time stamp.
> */
> - alternative_2("", "mfence", X86_FEATURE_MFENCE_RDTSC,
> - "lfence", X86_FEATURE_LFENCE_RDTSC);
> + ifence();
> return rdtsc();
> }
>
next prev parent reply other threads:[~2018-01-12 2:27 UTC|newest]
Thread overview: 139+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 0:46 [kernel-hardening] [PATCH v2 00/19] prevent bounds-check bypass via speculative execution Dan Williams
2018-01-12 0:46 ` Dan Williams
2018-01-12 0:46 ` Dan Williams
2018-01-12 0:46 ` [kernel-hardening] [PATCH v2 01/19] Documentation: document array_ptr Dan Williams
2018-01-12 0:46 ` Dan Williams
2018-01-12 10:38 ` [kernel-hardening] " Geert Uytterhoeven
2018-01-12 10:38 ` Geert Uytterhoeven
2018-01-12 10:38 ` Geert Uytterhoeven
2018-01-16 21:01 ` [kernel-hardening] " Kees Cook
2018-01-16 21:01 ` Kees Cook
2018-01-12 0:46 ` [kernel-hardening] [PATCH v2 02/19] arm64: implement ifence_array_ptr() Dan Williams
2018-01-12 0:46 ` Dan Williams
2018-01-12 0:46 ` [kernel-hardening] [PATCH v2 03/19] arm: " Dan Williams
2018-01-12 0:46 ` Dan Williams
2018-01-12 0:46 ` [kernel-hardening] [PATCH v2 04/19] x86: implement ifence() Dan Williams
2018-01-12 0:46 ` Dan Williams
2018-01-12 2:27 ` Eric W. Biederman [this message]
2018-01-12 2:27 ` Eric W. Biederman
2018-01-12 3:39 ` [kernel-hardening] " Dan Williams
2018-01-12 3:39 ` Dan Williams
2018-01-12 0:46 ` [kernel-hardening] [PATCH v2 05/19] x86: implement ifence_array_ptr() and array_ptr_mask() Dan Williams
2018-01-12 0:46 ` Dan Williams
2018-01-12 0:46 ` [kernel-hardening] [PATCH v2 06/19] asm-generic/barrier: mask speculative execution flows Dan Williams
2018-01-12 0:46 ` Dan Williams
2018-01-12 2:42 ` [kernel-hardening] " Eric W. Biederman
2018-01-12 2:42 ` Eric W. Biederman
2018-01-12 9:12 ` [kernel-hardening] " Peter Zijlstra
2018-01-12 9:12 ` Peter Zijlstra
2018-01-13 0:41 ` [kernel-hardening] " Dan Williams
2018-01-13 0:41 ` Dan Williams
2018-01-15 8:46 ` [kernel-hardening] " Peter Zijlstra
2018-01-15 8:46 ` Peter Zijlstra
2018-01-12 0:47 ` [kernel-hardening] [PATCH v2 07/19] x86: introduce __uaccess_begin_nospec and ASM_IFENCE Dan Williams
2018-01-12 0:47 ` Dan Williams
2018-01-12 17:51 ` [kernel-hardening] " Josh Poimboeuf
2018-01-12 17:51 ` Josh Poimboeuf
2018-01-12 18:21 ` [kernel-hardening] " Dan Williams
2018-01-12 18:21 ` Dan Williams
2018-01-12 18:58 ` [kernel-hardening] " Josh Poimboeuf
2018-01-12 18:58 ` Josh Poimboeuf
2018-01-12 19:26 ` [kernel-hardening] " Dan Williams
2018-01-12 19:26 ` Dan Williams
2018-01-12 20:01 ` [kernel-hardening] " Linus Torvalds
2018-01-12 20:01 ` Linus Torvalds
2018-01-12 20:41 ` [kernel-hardening] " Josh Poimboeuf
2018-01-12 20:41 ` Josh Poimboeuf
2018-01-12 0:47 ` [kernel-hardening] [PATCH v2 08/19] x86: use __uaccess_begin_nospec and ASM_IFENCE in get_user paths Dan Williams
2018-01-12 0:47 ` Dan Williams
2018-01-12 1:11 ` [kernel-hardening] " Linus Torvalds
2018-01-12 1:11 ` Linus Torvalds
2018-01-12 1:14 ` [kernel-hardening] " Dan Williams
2018-01-12 1:14 ` Dan Williams
2018-01-12 0:47 ` [kernel-hardening] [PATCH v2 09/19] ipv6: prevent bounds-check bypass via speculative execution Dan Williams
2018-01-12 0:47 ` Dan Williams
2018-01-12 0:47 ` [kernel-hardening] [PATCH v2 10/19] ipv4: " Dan Williams
2018-01-12 0:47 ` Dan Williams
2018-01-12 7:59 ` [kernel-hardening] " Greg KH
2018-01-12 7:59 ` Greg KH
2018-01-12 18:47 ` [kernel-hardening] " Dan Williams
2018-01-12 18:47 ` Dan Williams
2018-01-13 8:56 ` [kernel-hardening] " Greg KH
2018-01-13 8:56 ` Greg KH
2018-01-12 0:47 ` [kernel-hardening] [PATCH v2 11/19] vfs, fdtable: " Dan Williams
2018-01-12 0:47 ` Dan Williams
2018-01-12 0:47 ` [kernel-hardening] [PATCH v2 12/19] userns: " Dan Williams
2018-01-12 0:47 ` Dan Williams
2018-01-12 0:47 ` [kernel-hardening] [PATCH v2 13/19] udf: " Dan Williams
2018-01-12 0:47 ` Dan Williams
2018-01-15 10:32 ` [kernel-hardening] " Jan Kara
2018-01-15 10:32 ` Jan Kara
2018-01-15 17:49 ` [kernel-hardening] " Dan Williams
2018-01-15 17:49 ` Dan Williams
2018-01-12 0:47 ` [kernel-hardening] [PATCH v2 14/19] [media] uvcvideo: " Dan Williams
2018-01-12 0:47 ` Dan Williams
2018-08-06 21:40 ` Laurent Pinchart
2018-01-12 0:47 ` [kernel-hardening] [PATCH v2 15/19] carl9170: " Dan Williams
2018-01-12 0:47 ` Dan Williams
2018-01-12 14:42 ` [kernel-hardening] " Christian Lamparter
2018-01-12 14:42 ` Christian Lamparter
2018-01-12 18:39 ` [kernel-hardening] " Dan Williams
2018-01-12 18:39 ` Dan Williams
2018-01-12 20:01 ` [kernel-hardening] " Christian Lamparter
2018-01-12 20:01 ` Christian Lamparter
2018-01-12 23:05 ` [kernel-hardening] " Dan Williams
2018-01-12 23:05 ` Dan Williams
2018-01-12 0:47 ` [kernel-hardening] [PATCH v2 16/19] p54: " Dan Williams
2018-01-12 0:47 ` Dan Williams
2018-01-12 0:47 ` [kernel-hardening] [PATCH v2 17/19] qla2xxx: " Dan Williams
2018-01-12 0:47 ` Dan Williams
2018-01-12 1:19 ` [kernel-hardening] " James Bottomley
2018-01-12 1:19 ` James Bottomley
2018-01-12 5:38 ` [kernel-hardening] " Dan Williams
2018-01-12 5:38 ` Dan Williams
2018-01-12 6:05 ` [kernel-hardening] " James Bottomley
2018-01-12 6:05 ` James Bottomley
2018-01-12 0:48 ` [kernel-hardening] [PATCH v2 18/19] cw1200: " Dan Williams
2018-01-12 0:48 ` Dan Williams
2018-01-12 0:48 ` [kernel-hardening] [PATCH v2 19/19] net: mpls: " Dan Williams
2018-01-12 0:48 ` Dan Williams
2018-01-12 1:19 ` [kernel-hardening] Re: [PATCH v2 00/19] " Linus Torvalds
2018-01-12 1:19 ` Linus Torvalds
2018-01-12 1:19 ` Linus Torvalds
2018-01-12 1:19 ` Linus Torvalds
2018-01-12 1:41 ` [kernel-hardening] " Dan Williams
2018-01-12 1:41 ` Dan Williams
2018-01-12 1:41 ` Dan Williams
2018-01-12 1:41 ` Dan Williams
2018-01-18 13:18 ` [kernel-hardening] " Will Deacon
2018-01-18 13:18 ` Will Deacon
2018-01-18 13:18 ` Will Deacon
2018-01-18 13:18 ` Will Deacon
2018-01-18 13:18 ` Will Deacon
2018-01-18 13:18 ` Will Deacon
2018-01-18 16:58 ` [kernel-hardening] " Dan Williams
2018-01-18 16:58 ` Dan Williams
2018-01-18 16:58 ` Dan Williams
2018-01-18 16:58 ` Dan Williams
2018-01-18 17:05 ` [kernel-hardening] " Will Deacon
2018-01-18 17:05 ` Will Deacon
2018-01-18 17:05 ` Will Deacon
2018-01-18 17:05 ` Will Deacon
2018-01-18 21:41 ` [kernel-hardening] " Laurent Pinchart
2018-01-18 21:41 ` Laurent Pinchart
2018-01-18 21:41 ` Laurent Pinchart
2018-01-18 21:41 ` Laurent Pinchart
2018-01-18 21:41 ` Laurent Pinchart
2018-01-13 0:15 ` [kernel-hardening] " Tony Luck
2018-01-13 0:15 ` Tony Luck
2018-01-13 0:15 ` Tony Luck
2018-01-13 18:51 ` [kernel-hardening] " Linus Torvalds
2018-01-13 18:51 ` Linus Torvalds
2018-01-13 18:51 ` Linus Torvalds
2018-01-16 19:21 ` [kernel-hardening] " Tony Luck
2018-01-16 19:21 ` Tony Luck
2018-01-16 19:21 ` Tony Luck
2018-01-12 10:02 ` [kernel-hardening] " Russell King - ARM Linux
2018-01-12 10:02 ` Russell King - ARM Linux
2018-01-12 10:02 ` Russell King - ARM Linux
2018-01-12 10:02 ` Russell King - ARM Linux
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=87efmv4xr2.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=alan.cox@intel.com \
--cc=alan@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=elena.reshetova@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.