mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Tal Zussman <tz2294@columbia.edu>
Cc: wangfushuai <wangfushuai@baidu.com>,
	corbet@lwn.net, david@redhat.com, andrii@kernel.org,
	npache@redhat.com, catalin.marinas@arm.com, xu.xin16@zte.com.cn,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: proc: update VmFlags documentation in smaps
Date: Sat, 7 Jun 2025 14:25:05 -0700	[thread overview]
Message-ID: <20250607142505.e58fda734ce54167724705a3@linux-foundation.org> (raw)
In-Reply-To: <CAKha_so-2Z+4rAKezv1peeWdkOKoMMvuLqq7dhOmbeeAGxHF5Q@mail.gmail.com>

On Sat, 7 Jun 2025 13:03:30 -0400 Tal Zussman <tz2294@columbia.edu> wrote:

> On Sat, Jun 7, 2025 at 11:36 AM wangfushuai <wangfushuai@baidu.com> wrote:
> > Remove outdated VM_DENYWRITE("dw") reference and add missing
> > VM_LOCKONFAULT("lf") and VM_UFFD_MINOR("ui") flags.
> 
> VM_DROPPABLE ("dp") is also missing, would be nice to add it as well.
> 

Thanks.  How's this?


--- a/Documentation/filesystems/proc.rst~docs-proc-update-vmflags-documentation-in-smaps-fix
+++ a/Documentation/filesystems/proc.rst
@@ -610,6 +610,7 @@ encoded manner. The codes are the follow
     ss    shadow/guarded control stack page
     sl    sealed
     lf    lock on fault pages
+    dp    always lazily freeable mapping
     ==    =======================================
 
 Note that there is no guarantee that every flag and associated mnemonic will
_


  parent reply	other threads:[~2025-06-07 21:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-07 15:36 wangfushuai
     [not found] ` <CAKha_so-2Z+4rAKezv1peeWdkOKoMMvuLqq7dhOmbeeAGxHF5Q@mail.gmail.com>
2025-06-07 21:25   ` Andrew Morton [this message]
2025-06-08  2:57     ` wangfushuai

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=20250607142505.e58fda734ce54167724705a3@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=andrii@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=david@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npache@redhat.com \
    --cc=tz2294@columbia.edu \
    --cc=wangfushuai@baidu.com \
    --cc=xu.xin16@zte.com.cn \
    /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
all inboxes | Powered by JetHome®