Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S933330AbcLMOUl (ORCPT <rfc822;w@1wt.eu>);
        Tue, 13 Dec 2016 09:20:41 -0500
Received: from mx1.redhat.com ([209.132.183.28]:51800 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S932515AbcLMOUk (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 13 Dec 2016 09:20:40 -0500
Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley
        Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United
        Kingdom.
        Registered in England and Wales under Company Registration No. 3798903
From: David Howells <dhowells@redhat.com>
In-Reply-To: <a5615075-dd39-e206-cbce-385bed72473f@gmail.com>
References: <a5615075-dd39-e206-cbce-385bed72473f@gmail.com> <CAKgNAkh9JLN4P+Fu+yRCNo96E3VwjYLRquuaf43XRWeuC7gnNw@mail.gmail.com> <51643019-bb42-4066-c824-c55b9e668ac6@man7.org> <25262.1481628931@warthog.procyon.org.uk> <9f32a79b-5795-bff4-b741-bf927a525149@gmail.com> <26913.1481636296@warthog.procyon.org.uk>
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
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <30565.1481638837.1@warthog.procyon.org.uk>
Date: Tue, 13 Dec 2016 14:20:37 +0000
Message-ID: <30566.1481638837@warthog.procyon.org.uk>
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Tue, 13 Dec 2016 14:20:39 +0000 (UTC)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 801
Lines: 15

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