Subject: Re: [PATCH] [v2] x86/doc: add PTI description
To: Dave Hansen <dave.hansen@linux.intel.com>,
        linux-kernel@vger.kernel.org
Cc: x86@kernel.org
References: <20180105002428.19A01A83@viggo.jf.intel.com>
From: Hector Martin 'marcan' <marcan@marcan.st>
Message-ID: <2a2f0da6-3059-3ae5-8e39-48046389ebc9@marcan.st>
Date: Fri, 5 Jan 2018 10:43:28 +0900
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <20180105002428.19A01A83@viggo.jf.intel.com>
Content-Type: text/plain; charset=utf-8
Content-Language: es-ES
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org

On 2018-01-05 09:24, Dave Hansen wrote:
> +			Not specifying this option nothing is equivalent to
> +			pti=auto.

-nothing

> +Page Table Isolation (pti, previously known as KAISER[1]) is a
> +countermeasure against attacks on kernel address information such
> +as the "Meltdown" approach[2].

It's not really just address information, but any data. Maybe "attacks
that leak kernel memory"?

> +To avoid leaking address information, we create an new, independent

Same issue here. Also an -> a.

> +copy of the page tables which are used only when running userspace

are -> is. The copy is singular.

> +applications.  When the kernel is entered via syscalls, interrupts or
> +exceptions, page tables are switched to the full "kernel" copy.  When

"the page tables".

> +crippled by setting the NX bit in the top level.  This ensures
> +that if a kernel->user CR3 switch is missed that userspace will
> +crash immediately upon executing its first instruction.

"that userspace" -> "then userspace"

-- 
Hector Martin "marcan" (marcan@marcan.st)
Public Key: https://mrcn.st/pub