From: wangfushuai <wangfushuai@baidu.com>
To: <corbet@lwn.net>, <akpm@linux-foundation.org>, <david@redhat.com>,
<andrii@kernel.org>, <npache@redhat.com>,
<catalin.marinas@arm.com>, <xu.xin16@zte.com.cn>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-doc@vger.kernel.org>, wangfushuai <wangfushuai@baidu.com>
Subject: [PATCH] docs: proc: update VmFlags documentation in smaps
Date: Sat, 7 Jun 2025 23:36:14 +0800 [thread overview]
Message-ID: <20250607153614.81914-1-wangfushuai@baidu.com> (raw)
Remove outdated VM_DENYWRITE("dw") reference and add missing
VM_LOCKONFAULT("lf") and VM_UFFD_MINOR("ui") flags.
Signed-off-by: wangfushuai <wangfushuai@baidu.com>
---
Documentation/filesystems/proc.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
index 2a17865dfe39..e48dabab2a4a 100644
--- a/Documentation/filesystems/proc.rst
+++ b/Documentation/filesystems/proc.rst
@@ -584,7 +584,6 @@ encoded manner. The codes are the following:
ms may share
gd stack segment growns down
pf pure PFN range
- dw disabled write to the mapped file
lo pages are locked in memory
io memory mapped I/O area
sr sequential read advise provided
@@ -607,8 +606,10 @@ encoded manner. The codes are the following:
mt arm64 MTE allocation tags are enabled
um userfaultfd missing tracking
uw userfaultfd wr-protect tracking
+ ui userfaultfd minor fault
ss shadow/guarded control stack page
sl sealed
+ lf lock on fault pages
== =======================================
Note that there is no guarantee that every flag and associated mnemonic will
--
2.36.1
next reply other threads:[~2025-06-07 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 15:36 wangfushuai [this message]
[not found] ` <CAKha_so-2Z+4rAKezv1peeWdkOKoMMvuLqq7dhOmbeeAGxHF5Q@mail.gmail.com>
2025-06-07 21:25 ` Andrew Morton
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=20250607153614.81914-1-wangfushuai@baidu.com \
--to=wangfushuai@baidu.com \
--cc=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=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®