From: Josh Poimboeuf <jpoimboe@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 0/8] L1TFv7 3
Date: Fri, 8 Jun 2018 17:37:27 -0500 [thread overview]
Message-ID: <20180608223727.6szirt3236nrwmbo@treble> (raw)
In-Reply-To: <20180607232238.671B3610FB@crypto-ml.lab.linutronix.de>
On Thu, Jun 07, 2018 at 04:22:20PM -0700, speck for ak_at_linux.intel.com wrote:
> From: Andi Kleen <ak@linux.intel.com>
> Subject: L1TFv7
>
> This is the native OS mitigation for L1TF attacks using page table inversion,
> and adding the sysfs reporting.
>
> Additional mitigations are still needed for KVM.
>
> Addresses all left over review comments. Only very minor changes compared
> to last version.
>
> Andi Kleen (7):
> x86/speculation/l1tf: Increase 32bit PAE __PHYSICAL_PAGE_MASK
> x86/speculation/l1tf: Protect PROT_NONE PTEs against speculation
> x86/speculation/l1tf: Make sure the first page is always reserved
> x86/speculation/l1tf: Add sysfs reporting for l1tf
> x86/speculation/l1tf: Report if too much memory for L1TF workaround
> x86/speculation/l1tf: Disallow non privileged high MMIO PROT_NONE
> mappings
> x86/speculation/l1tf: Limit swap file size to MAX_PA/2
>
> Linus Torvalds (1):
> x86/speculation/l1tf: Protect swap entries against L1TF
Reviewed-by: Josh Poimboeuf <jpoimboe@redhat.com>
--
Josh
next parent reply other threads:[~2018-06-08 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180607232238.671B3610FB@crypto-ml.lab.linutronix.de>
2018-06-08 22:37 ` Josh Poimboeuf [this message]
[not found] <20180607232235.139FA61029@crypto-ml.lab.linutronix.de>
2018-06-07 23:39 ` [MODERATED] Re: [PATCH 0/8] L1TFv7 3 Dave Hansen
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=20180608223727.6szirt3236nrwmbo@treble \
--to=jpoimboe@redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).