From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: "Ian Rogers" <irogers@google.com>,
"Rik van Riel" <riel@redhat.com>,
linux-man@vger.kernel.org, LKML <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: Re: [PATCH] proc.5: add "wf" to VmFlags in /proc/[pid]/smaps
Date: Mon, 25 May 2020 17:59:06 +0300 [thread overview]
Message-ID: <20200525145906.e5xfzmj6hvl7t4fg@box> (raw)
In-Reply-To: <1edcb7ac-bc5f-b9ec-a037-656005ae85e3@gmail.com>
On Mon, May 25, 2020 at 03:50:38PM +0200, Michael Kerrisk (man-pages) wrote:
> On 5/22/20 1:13 AM, Ian Rogers wrote:
> > On Thu, May 21, 2020 at 3:25 PM Ian Rogers <irogers@google.com> wrote:
> >>
> >> 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>
> >
> > Doing a quick audit of fs/proc/task_mmu.c having noticed this flag was
> > missing I note:
> > - "mp" isn't documented, only possible with INTEL_MPX
> > - "nl" is documented but not present in show_smap_vma_flags
> > - "um" and "uw" aren't documented
>
> I took a shot at fixing these:
>
>
> mp - MPX-specific VMA (x86, since Linux 3.19)
This one is gone. The patch to remove leftovers of MPX is linux-next.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2020-05-25 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 22:25 Ian Rogers
2020-05-21 23:13 ` Ian Rogers
2020-05-25 13:50 ` Michael Kerrisk (man-pages)
2020-05-25 14:59 ` Kirill A. Shutemov [this message]
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=20200525145906.e5xfzmj6hvl7t4fg@box \
--to=kirill@shutemov.name \
--cc=colm@allcosts.net \
--cc=fweimer@redhat.com \
--cc=irogers@google.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