From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7DD94C5ACCC for ; Thu, 18 Oct 2018 09:57:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 46A5A2083E for ; Thu, 18 Oct 2018 09:57:33 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 46A5A2083E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ucw.cz Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728114AbeJRR5p (ORCPT ); Thu, 18 Oct 2018 13:57:45 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:37043 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728071AbeJRR5o (ORCPT ); Thu, 18 Oct 2018 13:57:44 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id B2C0B808CC; Thu, 18 Oct 2018 11:57:26 +0200 (CEST) Date: Thu, 18 Oct 2018 11:57:27 +0200 From: Pavel Machek To: Jarkko Sakkinen Cc: x86@kernel.org, platform-driver-x86@vger.kernel.org, dave.hansen@intel.com, sean.j.christopherson@intel.com, nhorman@redhat.com, npmccallum@redhat.com, serge.ayoun@intel.com, shay.katz-zamir@intel.com, linux-sgx@vger.kernel.org, andriy.shevchenko@linux.intel.com, Jonathan Corbet , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , "open list:DOCUMENTATION" , open list Subject: Re: [PATCH v14 19/19] x86/sgx: Driver documentation Message-ID: <20181018095727.GC10861@amd> References: <20180925130845.9962-1-jarkko.sakkinen@linux.intel.com> <20180925130845.9962-20-jarkko.sakkinen@linux.intel.com> <20181015205436.GA28500@amd> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6zdv2QT/q3FMhpsV" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --6zdv2QT/q3FMhpsV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu 2018-10-18 02:45:27, Jarkko Sakkinen wrote: > On Mon, 15 Oct 2018, Pavel Machek wrote: > >On Tue 2018-09-25 16:06:56, Jarkko Sakkinen wrote: > >>+Intel(R) SGX is a set of CPU instructions that can be used by applicat= ions to > >>+set aside private regions of code and data. The code outside the encla= ve is > >>+disallowed to access the memory inside the enclave by the CPU access c= ontrol. > >>+In a way you can think that SGX provides inverted sandbox. It protects= the > >>+application from a malicious host. > > > >Well, recently hardware had some problems keeping its > >promises. So... what about rowhammer, meltdown and spectre? >=20 > Doesn't hardware always have this problem over time? No, not really. In this case, tries to protect from hardware "attacks" done by machine owner. That job is theoretically impossible, so you have harder situation than most.. > >Which ones apply, which ones do not, and on what cpu generations? >=20 > Definitely should be refined. >=20 > Meltdowns approach AFAIK does not work because reads outside the enclave > will always have a predefined value (-1) but only if the page is present, > which was later exploited in the Foreshadow attack. What about L1tf and https://github.com/lsds/spectre-attack-sgx ? Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --6zdv2QT/q3FMhpsV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlvIWQcACgkQMOfwapXb+vIbCwCgw3wWxvBiMbEy5TVWTbYyQmif TjkAniEwkld7XGcUBTl90sv+3trigWg1 =YAi6 -----END PGP SIGNATURE----- --6zdv2QT/q3FMhpsV--