The patch titled
Subject: docs-procs-describe-proc-pid-map_files-entry-fix
has been removed from the -mm tree. Its filename was
docs-procs-describe-proc-pid-map_files-entry-fix.patch
This patch was dropped because it was folded into docs-procs-describe-proc-pid-map_files-entry.patch
------------------------------------------------------
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: docs-procs-describe-proc-pid-map_files-entry-fix
tweaks
Cc: Cyrill Gorcunov <gorcunov@xxxxxxxxxx>
Cc: Kees Cook <keescook@xxxxxxxxxxxx>
Cc: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
Cc: Calvin Owens <calvinowens@xxxxxx>
Cc: Pavel Emelyanov <xemul@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/filesystems/proc.txt | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff -puN Documentation/filesystems/proc.txt~docs-procs-describe-proc-pid-map_files-entry-fix Documentation/filesystems/proc.txt
--- a/Documentation/filesystems/proc.txt~docs-procs-describe-proc-pid-map_files-entry-fix
+++ a/Documentation/filesystems/proc.txt
@@ -1766,8 +1766,8 @@ pair provide additional information part
3.9 /proc/<pid>/map_files - Information about memory mapped files
---------------------------------------------------------------------
-This directory consists of simbolic links which represent memory mapped files
-the process is carrying. A typical output is like the following
+This directory contains symbolic links which represent memory mapped files
+the process is maintaining. Example output:
| lr-------- 1 root root 64 Jan 27 11:24 333c600000-333c620000 -> /usr/lib64/ld-2.18.so
| lr-------- 1 root root 64 Jan 27 11:24 333c81f000-333c820000 -> /usr/lib64/ld-2.18.so
@@ -1776,15 +1776,15 @@ the process is carrying. A typical outpu
| lr-------- 1 root root 64 Jan 27 11:24 35d0421000-35d0422000 -> /usr/lib64/libselinux.so.1
| lr-------- 1 root root 64 Jan 27 11:24 400000-41a000 -> /usr/bin/ls
-The name of a link is virtual memory bounds a particular map exhibits, i.e.
+The name of a link represents the virtual memory bounds of a mapping, i.e.
vm_area_struct::vm_start-vm_area_struct::vm_end.
-The main purpose of map_files directory is to be able to retrieve a set of
-memory mapped files in a fast way instead of parsing /proc/<pid>/maps or
-/proc/<pid>/smaps which contain a way more records. Same time one can open(2)
-mappings from the listings of two processes and comparing inodes figure out
-which anonymous memory areas are actually shared.
-
+The main purpose of the map_files is to retrieve a set of memory mapped
+files in a fast way instead of parsing /proc/<pid>/maps or
+/proc/<pid>/smaps, both of which contain many more records. At the same
+time one can open(2) mappings from the listings of two processes and
+comparing their inode numbers to figure out which anonymous memory areas
+are actually shared.
------------------------------------------------------------------------------
Configuring procfs
_
Patches currently in -mm which might be from akpm@xxxxxxxxxxxxxxxxxxxx are
origin.patch
mm-page_allocc-__alloc_pages_nodemask-dont-alter-arg-gfp_mask.patch
vmscan-force-scan-offline-memory-cgroups.patch
mm-memcontrol-default-hierarchy-interface-for-memory.patch
mm-memcontrol-fold-move_anon-and-move_file.patch
mm-compaction-enhance-tracepoint-output-for-compaction-begin-end.patch
mm-thp-allocate-transparent-hugepages-on-local-node.patch
docs-procs-describe-proc-pid-map_files-entry.patch
mm-page_ext-remove-unnecessary-stack_trace-field-fix.patch
mm-fix-arithmetic-overflow-in-__vm_enough_memory-fix.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
