From: Rik van Riel <riel@redhat.com>
To: mtk.manpages@gmail.com
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>,
"Colm MacCártaigh" <colm@allcosts.net>,
"Mike Kravetz" <mike.kravetz@oracle.com>
Subject: [patch] madvise.2: Add MADV_WIPEONFORK documentation
Date: Thu, 14 Sep 2017 13:00:40 -0400 [thread overview]
Message-ID: <20170914130040.6faabb18@cuia.usersys.redhat.com> (raw)
Add MADV_WIPEONFORK and MADV_KEEPONFORK documentation to
madvise.2. The new functionality was recently merged by
Linus, and should be in the 4.14 kernel.
While documenting what EINVAL means for MADV_WIPEONFORK,
I realized that MADV_FREE has the same thing going on,
so I documented EINVAL for both in the ERRORS section.
This patch documents the following kernel commit:
commit d2cd9ede6e193dd7d88b6d27399e96229a551b19
Author: Rik van Riel <riel@redhat.com>
Date: Wed Sep 6 16:25:15 2017 -0700
mm,fork: introduce MADV_WIPEONFORK
Signed-off-by: Rik van Riel <riel@redhat.com>
index dfb31b63dba3..4f987ddfae79 100644
--- a/man2/madvise.2
+++ b/man2/madvise.2
@@ -31,6 +31,8 @@
.\" 2010-06-19, Andi Kleen, Add documentation of MADV_SOFT_OFFLINE.
.\" 2011-09-18, Doug Goldstein <cardoe@cardoe.com>
.\" Document MADV_HUGEPAGE and MADV_NOHUGEPAGE
+.\" 2017-09-14, Rik van Riel <riel@redhat.com>
+.\" Document MADV_WIPEONFORK and MADV_KEEPONFORK
.\"
.TH MADVISE 2 2017-07-13 "Linux" "Linux Programmer's Manual"
.SH NAME
@@ -405,6 +407,22 @@ can be applied only to private anonymous pages (see
.BR mmap (2)).
On a swapless system, freeing pages in a given range happens instantly,
regardless of memory pressure.
+.TP
+.BR MADV_WIPEONFORK " (since Linux 4.14)"
+Present the child process with zero-filled memory in this range after a
+.BR fork (2).
+This is useful for per-process data in forking servers that should be
+re-initialized in the child process after a fork, for example PRNG seeds,
+cryptographic data, etc.
+.IP
+The
+.B MADV_WIPEONFORK
+operation can only be applied to private anonymous pages (see
+.BR mmap (2)).
+.TP
+.BR MADV_KEEPONFORK " (since Linux 4.14)"
+Undo the effect of an earlier
+.BR MADV_WIPEONFORK .
.SH RETURN VALUE
On success,
.BR madvise ()
@@ -457,6 +475,18 @@ or
but the kernel was not configured with
.BR CONFIG_KSM .
.TP
+.B EINVAL
+.I advice
+is
+.BR MADV_FREE
+or
+.BR MADV_WIPEONFORK
+but the specified address range includes file, Huge TLB,
+.BR MAP_SHARED ,
+or
+.BR VM_PFNMAP
+ranges.
+.TP
.B EIO
(for
.BR MADV_WILLNEED )
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-09-14 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 17:00 Rik van Riel [this message]
2017-09-14 17:09 ` [patch] madvise.2: Add MADV_WIPEONFORK documentation Colm MacCárthaigh
2017-09-14 19:05 ` [patch v2] " Rik van Riel
2017-09-14 19:10 ` Colm MacCárthaigh
2017-09-19 19:07 ` Michael Kerrisk (man-pages)
2017-09-19 19:21 ` Rik van Riel
2017-10-09 19:06 ` Michael Kerrisk (man-pages)
2017-10-09 19:08 ` Rik van Riel
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=20170914130040.6faabb18@cuia.usersys.redhat.com \
--to=riel@redhat.com \
--cc=colm@allcosts.net \
--cc=fweimer@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=mtk.manpages@gmail.com \
--cc=nilal@redhat.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;
as well as URLs for NNTP newsgroup(s).