mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Andy Isaacson <adi@hexapodia.org>
Cc: Pavel Machek <pavel@ucw.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Some highmem pages still in use after shrink_all_memory()?
Date: Mon, 08 Mar 2004 18:41:40 +1300	[thread overview]
Message-ID: <1078724500.21062.7.camel@laptop-linux.wpcb.org.au> (raw)
In-Reply-To: <20040308063639.GA20793@hexapodia.org>

Hi.

On Mon, 2004-03-08 at 19:36, Andy Isaacson wrote:
> Note that there are some applications for which it is a *bug* if an
> mlocked page gets written out to magnetic media.  (gpg, for example.)
> I imagine that they'd rather lose the mapping and get a page fault on
> the next reference (which they can then fix up with a new mmap and
> mlock) than have precious key material written to disk.

For such an application, we'd have to provide a mechanism to allow an
application to set/clear a page's Nosave flag. We'd probably also want
to be able to notify user space that a suspend cycle has just occurred
and the page contents are invalid.

> However, I don't see how to implement a cryptographically secure swsusp.

It would be possible with Suspend2 - one could implement a backend (page
transformer or writer) that implemented encryption and required the user
to enter a passphrase at resume time.

> (The importance of this behavior is obviously dependent on your threat
> model.  Perhaps the Sufficiently Paranoid gpg users will simply need to
> avoid using swsusp.)

Yes. Or close all gpg apps before suspending?

Nigel

-- 
Nigel Cunningham
C/- Westminster Presbyterian Church Belconnen
61 Templeton Street, Cook, ACT 2614.
+61 (2) 6251 7727(wk); +61 (2) 6253 0250 (home)

Evolution (n): A hypothetical process whereby infinitely improbable events occur 
with alarming frequency, order arises from chaos, and no one is given credit.


  reply	other threads:[~2004-03-08  7:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07 14:49 Pavel Machek
2004-03-08  0:40 ` Andrew Morton
2004-03-08  6:36   ` Andy Isaacson
2004-03-08  5:41     ` Nigel Cunningham [this message]
2004-03-08  9:13     ` Pavel Machek
2004-03-08  9:39     ` Arjan van de Ven
2004-03-08 15:09       ` Chris Friesen
2004-03-08 15:16         ` Arjan van de Ven
2004-03-08 15:35           ` Chris Friesen
2004-03-08 17:54             ` Zwane Mwaikambo
2004-03-08 16:36       ` Andy Isaacson
2004-03-08 18:34         ` Pavel Machek
2004-03-08 18:52           ` Andy Isaacson

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=1078724500.21062.7.camel@laptop-linux.wpcb.org.au \
    --to=ncunningham@users.sourceforge.net \
    --cc=adi@hexapodia.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®