From: Chris Friesen <cfriesen@nortelnetworks.com>
To: arjanv@redhat.com
Cc: Andy Isaacson <adi@hexapodia.org>, Pavel Machek <pavel@ucw.cz>,
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 10:09:47 -0500 [thread overview]
Message-ID: <404C8CBB.1030008@nortelnetworks.com> (raw)
In-Reply-To: 1078738772.4678.5.camel@laptop.fenrus.com
Arjan van de Ven 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.)
>>
>
> mlock() does not guarantee things not hitting magnetic media, just as
> mlock() doesn't guarantee that the physical address of a page doesn't
> change.
The mlock() man page sure seems to hint that they do, by explicitly
describing its use by high-security data processing as a way to keep the
information from getting to disk. There also seem to be a lot of
references on the web about using mlock() in secure programming.
Something is not right...
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2004-03-08 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 14:49 Some highmem pages still in use after shrink_all_memory()? Pavel Machek
2004-03-08 0:40 ` Andrew Morton
2004-03-08 6:36 ` Andy Isaacson
2004-03-08 5:41 ` Nigel Cunningham
2004-03-08 9:13 ` Pavel Machek
2004-03-08 9:39 ` Arjan van de Ven
2004-03-08 15:09 ` Chris Friesen [this message]
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=404C8CBB.1030008@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=adi@hexapodia.org \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--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 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.