Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [PATCH RFC v2 0/6] x86: Disabling PTI in compatibility mode
From:   Nadav Amit <nadav.amit@gmail.com>
In-Reply-To: <27a0082c-fadb-792a-740e-70932d51f1b5@linux.intel.com>
Date:   Thu, 15 Feb 2018 16:25:32 -0800
Cc:     Ingo Molnar <mingo@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Andy Lutomirski <luto@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Willy Tarreau <w@1wt.eu>, x86@kernel.org,
        linux-kernel@vger.kernel.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <91CEEFA7-86C8-4731-BC7E-6AF5CC3A1BA4@gmail.com>
References: <20180215163602.61162-1-namit@vmware.com>
 <27a0082c-fadb-792a-740e-70932d51f1b5@linux.intel.com>
To:     Dave Hansen <dave.hansen@linux.intel.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Dave Hansen <dave.hansen@linux.intel.com> wrote:

> On 02/15/2018 08:35 AM, Nadav Amit wrote:
>> I removed the PTI disabling while SMEP is unsupported, although I
>> must admit I did not fully understand why it is required.
>=20
> Do you mean you don't fully understand how PTI gives SMEP-like =
behavior
> on non-SMEP hardware?

No. I understand how it provide SMEP-like behavior, and I understand the =
value
of SMEP by itself.

However, I do not understand why SMEP-like protection is required to =
protect
processes that run in compatibility-mode from Meltdown/Spectre attacks. =
As
far as I understand, the process should not be able to manipulate the =
kernel
to execute code in the low 4GB.