mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: dhowells@redhat.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: Tue, 13 Dec 2016 14:20:37 +0000	[thread overview]
Message-ID: <30566.1481638837@warthog.procyon.org.uk> (raw)
In-Reply-To: <a5615075-dd39-e206-cbce-385bed72473f@gmail.com>

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"?

David

  parent reply	other threads:[~2016-12-13 14:20 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 [this message]
2016-12-14  7:27         ` Michael Kerrisk (man-pages)
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=30566.1481638837@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=evgsyr@gmail.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.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

Powered by JetHome