From: Rik van Riel <riel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Colm MacCárthaigh"
<colm-ZXBCfW2eEe/k1uMJSBkQmQ@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
nilal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Florian Weimer <fweimer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Mike Kravetz
<mike.kravetz-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Subject: Re: [patch v2] madvise.2: Add MADV_WIPEONFORK documentation
Date: Tue, 19 Sep 2017 15:21:47 -0400 [thread overview]
Message-ID: <1505848907.5486.9.camel@redhat.com> (raw)
In-Reply-To: <a1715d1d-7a03-d2db-7a8a-8a2edceae5d1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
On Tue, 2017-09-19 at 21:07 +0200, Michael Kerrisk (man-pages) wrote:
> Thanks. I applied this, and tweaked the madvise.2 text a little, to
> read as follows (please let me know if I messed anything up):
>
> MADV_WIPEONFORK (since Linux 4.14)
> Present the child process with zero-filled
> memory in this
> range after a fork(2). This is useful in forking
> servers
> in order to ensure that sensitive per-
> process data (for
> example, PRNG seeds, cryptographic secrets, and so
> on) is
> not handed to child processes.
>
> The MADV_WIPEONFORK operation can be applied
> only to pri‐
> vate anonymous pages (see mmap(2)).
That looks great. Thank you, Michael!
--
All rights reversed
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
"Colm MacCárthaigh" <colm@allcosts.net>
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-api@vger.kernel.org, nilal@redhat.com,
Florian Weimer <fweimer@redhat.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: [patch v2] madvise.2: Add MADV_WIPEONFORK documentation
Date: Tue, 19 Sep 2017 15:21:47 -0400 [thread overview]
Message-ID: <1505848907.5486.9.camel@redhat.com> (raw)
In-Reply-To: <a1715d1d-7a03-d2db-7a8a-8a2edceae5d1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
On Tue, 2017-09-19 at 21:07 +0200, Michael Kerrisk (man-pages) wrote:
> Thanks. I applied this, and tweaked the madvise.2 text a little, to
> read as follows (please let me know if I messed anything up):
>
> MADV_WIPEONFORK (since Linux 4.14)
> Present the child process with zero-filled
> memory in this
> range after a fork(2). This is useful in forking
> servers
> in order to ensure that sensitive per-
> process data (for
> example, PRNG seeds, cryptographic secrets, and so
> on) is
> not handed to child processes.
>
> The MADV_WIPEONFORK operation can be applied
> only to pri‐
> vate anonymous pages (see mmap(2)).
That looks great. Thank you, Michael!
--
All rights reversed
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-09-19 19:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 17:00 [patch] madvise.2: Add MADV_WIPEONFORK documentation Rik van Riel
2017-09-14 17:00 ` Rik van Riel
[not found] ` <20170914130040.6faabb18-3y8d1Ellc6BvD/m4c++uL6fLeoKvNuZc@public.gmane.org>
2017-09-14 17:09 ` Colm MacCárthaigh
2017-09-14 17:09 ` Colm MacCárthaigh
2017-09-14 17:09 ` Colm MacCárthaigh
[not found] ` <CAAF6GDdnY2AmzKx+t4ffCFxJ+RZS++4tmWvoazdVNVSYjra_WA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-14 19:05 ` [patch v2] " Rik van Riel
2017-09-14 19:05 ` Rik van Riel
2017-09-14 19:05 ` Rik van Riel
2017-09-14 19:10 ` Colm MacCárthaigh
2017-09-14 19:10 ` Colm MacCárthaigh
[not found] ` <20170914150546.74ad3a9a-3y8d1Ellc6BvD/m4c++uL6fLeoKvNuZc@public.gmane.org>
2017-09-19 19:07 ` Michael Kerrisk (man-pages)
2017-09-19 19:07 ` Michael Kerrisk (man-pages)
2017-09-19 19:07 ` Michael Kerrisk (man-pages)
[not found] ` <a1715d1d-7a03-d2db-7a8a-8a2edceae5d1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-19 19:21 ` Rik van Riel [this message]
2017-09-19 19:21 ` Rik van Riel
2017-10-09 19:06 ` Michael Kerrisk (man-pages)
2017-10-09 19:06 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkg8QJHfPfdfYXBU2-eW=_FWY99UYi_6hQejE=q5+66u1g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-09 19:08 ` Rik van Riel
2017-10-09 19:08 ` Rik van Riel
2017-10-09 19:08 ` Rik van Riel
[not found] ` <1507576124.21121.168.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-09 19:11 ` Michael Kerrisk (man-pages)
2017-10-09 19:11 ` Michael Kerrisk (man-pages)
2017-10-09 19:11 ` 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=1505848907.5486.9.camel@redhat.com \
--to=riel-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=colm-ZXBCfW2eEe/k1uMJSBkQmQ@public.gmane.org \
--cc=fweimer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mike.kravetz-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=nilal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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 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.