All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
To: Michael Kerrisk
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [PATCH] proc.5: Add info about /proc/[pid]/map_files directory (v2)
Date: Tue, 16 Apr 2013 21:37:37 +0400	[thread overview]
Message-ID: <516D8C61.5090004@parallels.com> (raw)

It was added into Linux v3.3 and provides info about files being mmap-ed in
a way _very_ similar to how /proc/[pid]/fd works. Thus I thought that the
best place for the map_files' doc is where where the fd's doc is.

v2: Added examples of how links look like and dependency on kernel config
option CONFIG_CHECKPOINT_RESTORE.

Signed-off-by: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>

---

diff --git a/man5/proc.5 b/man5/proc.5
index 520c5fc..1bfc63c 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -286,6 +286,42 @@ Thus the example command above could be written as:
 .RB "$" " foobar \-i /dev/stdin \-o /dev/stdout ..."
 .fi
 .in
+.TP
+.IR /proc/[pid]/map_files/ " (since kernel 3.3)
+This subdirectory contains entries corresponding to memory mapped
+files (see
+.BR mmap (2)).
+Entries are named by memory region start and end pair,
+and are symbolic links to the files themselves. Like this
+.in +4n
+.nf
+
+.RB "$" " ls -l /proc/self/map_files/" 
+lr--------. 1 root root 64 Apr 16 21:31 3252e00000-3252e20000 -> /usr/lib64/ld-2.15.so
+\&...
+.fi
+.in
+
+Although these entries are present for memory regions that were
+mapped with 
+.BR MAP_FILE
+flag, the way anonymous shared memory (regions created with
+.B MAP_ANON | MAP_SHARED
+flags)
+is implemented in Linux
+makes such regions also appear on this directory. In that case
+the target file would be the deleted /dev/zero one:
+.in +4n
+.nf
+
+.RB
+lrw-------. 1 root root 64 Apr 16 21:33 7fc075d2f000-7fc075e6f000 -> /dev/zero (deleted)
+.fi
+.in
+
+This directory appears only if the
+.B CONFIG_CHECKPOINT_RESTORE
+kernel configuration option is enabled.
 .\" FIXME Describe /proc/[pid]/loginuid
 .\"       Added in 2.6.11; updating requires CAP_AUDIT_CONTROL
 .\"       CONFIG_AUDITSYSCALL
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2013-04-16 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 17:37 Pavel Emelyanov [this message]
     [not found] ` <516D8C61.5090004-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-04-17  6:33   ` [PATCH] proc.5: Add info about /proc/[pid]/map_files directory (v2) 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=516D8C61.5090004@parallels.com \
    --to=xemul-bzqdu9zft3wakbo8gow8eq@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.