All of lore.kernel.org
 help / color / mirror / Atom feed
From: ak@linux.intel.com
To: speck@linutronix.de
Cc: Andi Kleen <ak@linux.intel.com>
Subject: [MODERATED] [PATCH v4 4/8] L1TFv4 7
Date: Wed,  9 May 2018 14:25:49 -0700	[thread overview]
Message-ID: <c75da7960a5888721ae8921a49dd485e8c97b3c3.1525900921.git.ak@linux.intel.com> (raw)
In-Reply-To: <cover.1525900921.git.ak@linux.intel.com>
In-Reply-To: <cover.1525900921.git.ak@linux.intel.com>

The L1TF workaround doesn't make any attempt to mitigate speculate
accesses to the first physical page for zeroed PTEs. Normally
it only contains some data from the early real mode BIOS.

I couldn't convince myself we always reserve the first page in
all configurations, so add an extra reservation call to
make sure it is really reserved. In most configurations (e.g.
with the standard reservations) it's likely a nop.

Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
 arch/x86/kernel/setup.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 6285697b6e56..fadbd41094d2 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -817,6 +817,9 @@ void __init setup_arch(char **cmdline_p)
 	memblock_reserve(__pa_symbol(_text),
 			 (unsigned long)__bss_stop - (unsigned long)_text);
 
+	/* Make sure page 0 is always reserved */
+	memblock_reserve(0, PAGE_SIZE);
+
 	early_reserve_initrd();
 
 	/*
-- 
2.14.3

  parent reply	other threads:[~2018-05-09 21:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 21:25 [MODERATED] [PATCH v4 0/8] L1TFv4 0 ak
2018-05-09 21:25 ` [MODERATED] [PATCH v4 1/8] L1TFv4 1 ak
2018-05-10 23:00   ` Thomas Gleixner
2018-05-10 23:18     ` [MODERATED] " Andi Kleen
2018-05-09 21:25 ` [MODERATED] [PATCH v4 2/8] L1TFv4 4 ak
2018-05-09 21:25 ` [MODERATED] [PATCH v4 3/8] L1TFv4 6 ak
2018-05-10 23:15   ` Thomas Gleixner
2018-05-10 23:32     ` [MODERATED] " Andi Kleen
2018-05-10 23:41       ` Thomas Gleixner
2018-05-09 21:25 ` ak [this message]
2018-05-09 21:25 ` [MODERATED] [PATCH v4 5/8] L1TFv4 8 ak
2018-05-10 23:27   ` Thomas Gleixner
2018-05-09 21:25 ` [MODERATED] [PATCH v4 6/8] L1TFv4 3 ak
2018-05-10 22:52   ` Thomas Gleixner
2018-05-10 23:26     ` [MODERATED] " Andi Kleen
2018-05-10 23:46       ` Thomas Gleixner
2018-05-09 21:25 ` [MODERATED] [PATCH v4 7/8] L1TFv4 2 ak
2018-05-11  8:23   ` Thomas Gleixner
2018-05-11  8:24   ` Thomas Gleixner
2018-05-09 21:25 ` [MODERATED] [PATCH v4 8/8] L1TFv4 5 ak
2018-05-10  4:13   ` [MODERATED] " Andi Kleen
2018-05-09 21:54 ` [MODERATED] Re: [PATCH v4 0/8] L1TFv4 0 Andi Kleen
2018-05-10  6:47 ` [MODERATED] Re: ***UNCHECKED*** " Vlastimil Babka
2018-05-10  8:04   ` Michal Hocko
2018-05-10 16:07     ` Andi Kleen
2018-05-10 16:57       ` [MODERATED] " Borislav Petkov
2018-05-10 17:35         ` Andi Kleen
2018-05-10 22:11           ` Thomas Gleixner
2018-05-10 22:26             ` [MODERATED] " Andi Kleen

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=c75da7960a5888721ae8921a49dd485e8c97b3c3.1525900921.git.ak@linux.intel.com \
    --to=ak@linux.intel.com \
    --cc=speck@linutronix.de \
    /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.