From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: mtk.manpages@gmail.com, lkml <linux-kernel@vger.kernel.org>,
Eugene Syromyatnikov <evgsyr@gmail.com>,
keyrings@vger.kernel.org, linux-man <linux-man@vger.kernel.org>
Subject: Re: Revised keyrings(7) man page for review
Date: Wed, 14 Dec 2016 08:27:22 +0100 [thread overview]
Message-ID: <2dea8ec1-0b1a-3d1e-da10-653a5d2f0838@gmail.com> (raw)
In-Reply-To: <30566.1481638837@warthog.procyon.org.uk>
On 12/13/2016 03:20 PM, David Howells wrote:
> Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> wrote:
>
>> The payload data may be stored in a tmpfs filesystem,
>> rather than in kernel memory, if the data size exceeds the
>> overhead of storing the data in the filesystem. (Storing
>> the data in a filesystem requires filesystem structures to
>> be allocated in the kernel. The size of these structures
>> determines the size threshold above which the tmpfs storage
>> method is used.) Since Linux 4.8, the payload data is
>> encrypted when stored in tmpfs, to prevent it being written
>> unencrypted into swap space.
>
> "... thereby preventing it from being written unencrypted into the swapspace"?
Fixed.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2016-12-14 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 15:47 Michael Kerrisk
2016-11-26 12:51 ` Michael Kerrisk (man-pages)
2016-12-13 11:35 ` David Howells
2016-12-13 12:43 ` Michael Kerrisk (man-pages)
2016-12-13 12:57 ` Michael Kerrisk (man-pages)
2016-12-13 13:38 ` David Howells
2016-12-13 13:52 ` Michael Kerrisk (man-pages)
2016-12-13 14:20 ` David Howells
2016-12-14 7:27 ` Michael Kerrisk (man-pages) [this message]
2016-12-13 13:31 ` David Howells
2016-12-13 13:41 ` Michael Kerrisk (man-pages)
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=2dea8ec1-0b1a-3d1e-da10-653a5d2f0838@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=dhowells@redhat.com \
--cc=evgsyr@gmail.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome