From: Jeremy Maitin-Shepard <jeremy@jeremyms.com>
To: Nigel Cunningham <ncunningham@crca.org.au>
Cc: tuxonice-devel@lists.tuxonice.net, linux-kernel@vger.kernel.org
Subject: Re: [TuxOnIce-devel] RFC: Suspend-to-ram cold boot protection by encrypting page cache
Date: Tue, 30 Jun 2009 23:43:53 -0700 [thread overview]
Message-ID: <87d48k2992.fsf@jeremyms.com> (raw)
In-Reply-To: <4A4B0125.2090502@crca.org.au> (Nigel Cunningham's message of "Wed, 01 Jul 2009 16:24:37 +1000")
Nigel Cunningham <ncunningham@crca.org.au> writes:
> Hi Jeremy.
> I'd suggest emailing the Linux-PM list rather than tuxonice-devel.
> TuxOnIce devel focuses on the out-of-vanilla suspend to disk
> enhancements rather than on suspend to ram.
The Linux-PM list is a good suggestion, but I specifically included
tuxonice because of the note at the bottom --- namely that I believe
that tuxonice in particular already includes support for much of what is
needed to implement the idea.
Specifically, suppose right at the stage in tuxonice hibernation when
the kernel as about to write the page cache pages to disk, it instead
just encrypts in place those pages, clears the encryption key, then
waits for the userspace helper to pass it back the key again to use to
decrypt the pages.
In fact it would seems that actually entering S3 is mostly irrelevant in
terms of the implementation.
Tuoxnice already has code to deal with interfacing with a userspace
helper that is kept unfrozen (and its pages handled specially) while
everything else is frozen and the page cache is overwritten, which is
precisely what is needed for this idea. In particular, it seems that an
implementation of the idea I proposed would look a lot like tuxonice
with a powerdown mode of entering S3, just that instead of writing the
page cache to disk, it is encrypted in place. I suppose it could well be that
all of the facilities used by tuxonice to do this are actually already
in the kernel, in which case it is indeed not relevant to tuxonice, but
it is not clear that the uswsusp infrastructure has everything that is
needed.
--
Jeremy Maitin-Shepard
next prev parent reply other threads:[~2009-07-01 6:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 6:07 RFC: Suspend-to-ram cold boot protection by encrypting page cache Jeremy Maitin-Shepard
2009-07-01 6:24 ` [TuxOnIce-devel] " Nigel Cunningham
2009-07-01 6:43 ` Jeremy Maitin-Shepard [this message]
2009-07-01 9:09 ` Nigel Cunningham
2009-07-01 15:55 ` Rafael J. Wysocki
2009-07-01 20:57 ` Jeremy Maitin-Shepard
2009-07-01 22:41 ` Rafael J. Wysocki
2009-07-01 22:58 ` Nigel Cunningham
2009-07-01 23:06 ` Jeremy Maitin-Shepard
2009-07-02 5:14 ` U Kuehn
2009-07-02 5:47 ` Jeremy Maitin-Shepard
2009-07-02 16:12 ` Rafael J. Wysocki
2009-07-04 2:44 ` Pavel Machek
2009-07-08 10:47 ` Jeremy Maitin-Shepard
2009-07-04 2:57 ` Pavel Machek
2009-07-08 11:09 ` Jeremy Maitin-Shepard
2009-07-09 10:14 ` Pavel Machek
2009-07-10 7:05 ` Jeremy Maitin-Shepard
2009-07-11 22:10 ` Pavel Machek
2009-07-01 12:21 ` Jens Gustedt
2009-07-01 20:40 ` Jeremy Maitin-Shepard
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=87d48k2992.fsf@jeremyms.com \
--to=jeremy@jeremyms.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@crca.org.au \
--cc=tuxonice-devel@lists.tuxonice.net \
/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.