From: Ian Rogers <irogers@google.com>
To: Rik van Riel <riel@redhat.com>, 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>,
"Ian Rogers" <irogers@google.com>
Subject: [PATCH] proc.5: add "wf" to VmFlags in /proc/[pid]/smaps
Date: Thu, 21 May 2020 15:25:51 -0700 [thread overview]
Message-ID: <20200521222551.259804-1-irogers@google.com> (raw)
This patch documents a flag added in 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
This was already documented in man2/madvise.2 in the commit:
commit c0c4f6c29c494c466f3a2a6273c5b55b76a72927
Author: Rik van Riel <riel@redhat.com>
Date: Tue Sep 19 20:32:00 2017 +0200
madvise.2: Document MADV_WIPEONFORK and MADV_KEEPONFORK
Signed-off-by: Ian Rogers <irogers@google.com>
---
man5/proc.5 | 1 +
1 file changed, 1 insertion(+)
diff --git a/man5/proc.5 b/man5/proc.5
index 46d603f28..3e5b91af0 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -2020,6 +2020,7 @@ encoded using the following two-letter codes:
ht - area uses huge tlb pages
nl - non-linear mapping
ar - architecture specific flag
+ wf - wipe on fork
dd - do not include area into core dump
sd - soft-dirty flag
mm - mixed map area
--
2.27.0.rc0.183.gde8f92d652-goog
next reply other threads:[~2020-05-21 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 22:25 Ian Rogers [this message]
2020-05-21 23:13 ` [PATCH] proc.5: add "wf" to VmFlags in /proc/[pid]/smaps Ian Rogers
2020-05-25 13:50 ` Michael Kerrisk (man-pages)
2020-05-25 14:59 ` Kirill A. Shutemov
2020-05-25 18:50 ` Michael Kerrisk (man-pages)
2020-05-25 13:48 ` 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=20200521222551.259804-1-irogers@google.com \
--to=irogers@google.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 \
--cc=riel@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).