From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: greg@enjellic.com
Cc: Pavel Machek <pavel@ucw.cz>,
platform-driver-x86@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Grzegorz Andrejczuk <grzegorz.andrejczuk@intel.com>,
Haim Cohen <haim.cohen@intel.com>, Ingo Molnar <mingo@kernel.org>,
Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>,
Jim Mattson <jmattson@google.com>,
Kan Liang <Kan.liang@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Kyle Huey <me@kylehuey.com>, Len Brown <len.brown@intel.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list:FILESYSTEMS (VFS and infrastructure)"
<linux-fsdevel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel>
Subject: Re: [PATCH v6 00/11] Intel SGX Driver
Date: Wed, 10 Jan 2018 18:16:56 +0200 [thread overview]
Message-ID: <20180110161656.hftp6lsnut7u6klr@linux.intel.com> (raw)
In-Reply-To: <201801092150.w09LoNtB017301@wind.enjellic.com>
On Tue, Jan 09, 2018 at 03:50:23PM -0600, Dr. Greg Wettstein wrote:
> > Everything going out of L1 gets encrypted. This is done to defend
> > against peripheral like adversaries and should work also against
> > meltdown.
>
> I don't believe this is an architecturally correct assertion. The
> encryption/decryption occurs at the 'bottom' of the cache heirarchy.
You are right and I was wrong. It is plain from L1 to LLC, which implies
as you correctly described potential cache missing attacks in addition
to timing attacks.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: greg@enjellic.com
Cc: Pavel Machek <pavel@ucw.cz>,
platform-driver-x86@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Grzegorz Andrejczuk <grzegorz.andrejczuk@intel.com>,
Haim Cohen <haim.cohen@intel.com>, Ingo Molnar <mingo@kernel.org>,
Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>,
Jim Mattson <jmattson@google.com>,
Kan Liang <Kan.liang@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Kyle Huey <me@kylehuey.com>, Len Brown <len.brown@intel.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list:FILESYSTEMS (VFS and infrastructure)"
<linux-fsdevel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Piotr Luc <piotr.luc@intel.com>,
Radim Kr??m???? <rkrcmar@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Tom Lendacky <thomas.lendacky@amd.com>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>
Subject: Re: [PATCH v6 00/11] Intel SGX Driver
Date: Wed, 10 Jan 2018 18:16:56 +0200 [thread overview]
Message-ID: <20180110161656.hftp6lsnut7u6klr@linux.intel.com> (raw)
In-Reply-To: <201801092150.w09LoNtB017301@wind.enjellic.com>
On Tue, Jan 09, 2018 at 03:50:23PM -0600, Dr. Greg Wettstein wrote:
> > Everything going out of L1 gets encrypted. This is done to defend
> > against peripheral like adversaries and should work also against
> > meltdown.
>
> I don't believe this is an architecturally correct assertion. The
> encryption/decryption occurs at the 'bottom' of the cache heirarchy.
You are right and I was wrong. It is plain from L1 to LLC, which implies
as you correctly described potential cache missing attacks in addition
to timing attacks.
/Jarkko
next prev parent reply other threads:[~2018-01-10 16:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 21:50 [PATCH v6 00/11] Intel SGX Driver Dr. Greg Wettstein
2018-01-09 21:50 ` Dr. Greg Wettstein
2018-01-10 16:16 ` Jarkko Sakkinen [this message]
2018-01-10 16:16 ` Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
2018-01-05 9:50 Dr. Greg Wettstein
2018-01-04 21:09 Dr. Greg Wettstein
2018-01-04 21:09 ` Dr. Greg Wettstein
2018-01-04 9:06 Dr. Greg Wettstein
2018-01-04 9:06 ` Dr. Greg Wettstein
2018-01-09 14:25 ` Jarkko Sakkinen
2018-01-09 14:25 ` Jarkko Sakkinen
2018-01-04 8:02 Dr. Greg Wettstein
2018-01-04 9:20 ` Christian Stroetmann
2018-01-03 0:59 Dr. Greg Wettstein
2018-01-03 0:59 ` Dr. Greg Wettstein
2018-01-03 2:00 ` Christian Stroetmann
2018-01-03 9:48 ` Pavel Machek
2018-01-03 9:48 ` Pavel Machek
2017-12-27 10:30 Dr. Greg Wettstein
2017-12-27 10:30 ` Dr. Greg Wettstein
2017-12-27 20:46 ` Pavel Machek
2017-12-27 20:46 ` Pavel Machek
2017-11-25 19:29 Jarkko Sakkinen
2017-11-25 19:29 ` Jarkko Sakkinen
2017-12-12 14:07 ` Pavel Machek
2017-12-12 14:07 ` Pavel Machek
2017-12-14 11:18 ` Jarkko Sakkinen
2017-12-14 11:18 ` Jarkko Sakkinen
2017-12-19 23:33 ` Jarkko Sakkinen
2017-12-19 23:33 ` Jarkko Sakkinen
2017-12-20 13:18 ` Jarkko Sakkinen
2017-12-20 13:18 ` Jarkko Sakkinen
2018-01-04 14:17 ` Cedric Blancher
2018-01-04 14:17 ` Cedric Blancher
2018-01-04 14:27 ` Greg Kroah-Hartman
2018-01-04 14:27 ` Greg Kroah-Hartman
2018-01-04 19:18 ` Ozgur
2018-01-04 15:08 ` James Bottomley
2018-01-04 15:08 ` James Bottomley
2018-01-09 14:27 ` Jarkko Sakkinen
2018-01-09 14:27 ` Jarkko Sakkinen
2018-02-08 8:46 ` Pavel Machek
2018-02-08 8:46 ` Pavel Machek
2018-02-08 13:48 ` Jarkko Sakkinen
2018-02-08 13:48 ` Jarkko Sakkinen
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=20180110161656.hftp6lsnut7u6klr@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=Janakarajan.Natarajan@amd.com \
--cc=Kan.liang@intel.com \
--cc=bp@suse.de \
--cc=davem@davemloft.net \
--cc=greg@enjellic.com \
--cc=gregkh@linuxfoundation.org \
--cc=grzegorz.andrejczuk@intel.com \
--cc=haim.cohen@intel.com \
--cc=jmattson@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel \
--cc=me@kylehuey.com \
--cc=mingo@kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=x86@kernel.org \
/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.