From: Pavel Machek <pavel@ucw.cz>
To: Joseph Cihula <joseph.cihula@intel.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
arjan@linux.intel.com, hpa@zytor.com, andi@firstfloor.org,
chrisw@sous-sol.org, jmorris@namei.org, jbeulich@novell.com,
peterm@redhat.com, gang.wei@intel.com, shane.wang@intel.com
Subject: Re: [RFC v5][PATCH 3/4] intel_txt: Intel(R) TXT Sx shutdown support
Date: Wed, 24 Jun 2009 17:05:06 +0200 [thread overview]
Message-ID: <20090624150506.GK1784@ucw.cz> (raw)
In-Reply-To: <4A4024C2.3050107@intel.com>
On Mon 2009-06-22 17:41:38, Joseph Cihula wrote:
> Support for graceful handling of sleep states (S3/S4/S5) after an Intel(R) TXT launch.
>
> Without this patch, attempting to place the system in one of the ACPI sleep
> states (S3/S4/S5) will cause the TXT hardware to treat this as an attack and
> will cause a system reset, with memory locked. Not only may the subsequent
> memory scrub take some time, but the platform will be unable to enter the
> requested power state.
>
> This patch calls back into the tboot so that it may properly and securely clean
> up system state and clear the secrets-in-memory flag, after which it will place
> the system into the requested sleep state using ACPI information passed by the kernel.
I don't get this. In case of hibernation... how do you 'protect' the
data in memory?
This really needs big Documentation/ patch explaining the design
before it can be reviewed properly.
What does it protect? All kernel memory? How does it handle S3? Who
does encryption for hibernation?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-06-27 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 0:41 [RFC v5][PATCH 3/4] intel_txt: Intel(R) TXT Sx shutdown support Joseph Cihula
2009-06-24 15:05 ` Pavel Machek [this message]
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=20090624150506.GK1784@ucw.cz \
--to=pavel@ucw.cz \
--cc=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=chrisw@sous-sol.org \
--cc=gang.wei@intel.com \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=jmorris@namei.org \
--cc=joseph.cihula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterm@redhat.com \
--cc=shane.wang@intel.com \
/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