From: Mike Kravetz <mike.kravetz@oracle.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, Michal Hocko <mhocko@suse.com>,
Andrea Arcangeli <aarcange@redhat.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: [patch] mremap.2: Add description of old_size == 0 functionality
Date: Fri, 15 Sep 2017 14:37:45 -0700 [thread overview]
Message-ID: <20170915213745.6821-1-mike.kravetz@oracle.com> (raw)
Since at least the 2.6 time frame, mremap would create a new mapping
of the same pages if 'old_size == 0'. It would also leave the original
mapping. This was used to create a 'duplicate mapping'.
Document the behavior and return codes. But, also mention that the
functionality is deprecated and discourage its use.
A recent change was made to mremap so that an attempt to create a
duplicate a private mapping will fail.
commit dba58d3b8c5045ad89c1c95d33d01451e3964db7
Author: Mike Kravetz <mike.kravetz@oracle.com>
Date: Wed Sep 6 16:20:55 2017 -0700
mm/mremap: fail map duplication attempts for private mappings
This return code is also documented here.
Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
---
man2/mremap.2 | 23 ++++++++++++++++++++++-
1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/man2/mremap.2 b/man2/mremap.2
index 98643c640..98df7d5fa 100644
--- a/man2/mremap.2
+++ b/man2/mremap.2
@@ -58,6 +58,21 @@ may be provided; see the description of
.B MREMAP_FIXED
below.
.PP
+If the value of \fIold_size\fP is zero, and \fIold_address\fP refers to
+a private anonymous mapping, then
+.BR mremap ()
+will create a new mapping of the same pages. \fInew_size\fP
+will be the size of the new mapping and the location of the new mapping
+may be specified with \fInew_address\fP, see the description of
+.B MREMAP_FIXED
+below. If a new mapping is requested via this method, then the
+.B MREMAP_MAYMOVE
+flag must also be specified. This functionality is deprecated, and no
+new code should be written to use this feature. A better method of
+obtaining multiple mappings of the same private anonymous memory is via the
+.BR memfd_create()
+system call.
+.PP
In Linux the memory is divided into pages.
A user process has (one or)
several linear virtual memory segments.
@@ -174,7 +189,12 @@ and
or
.B MREMAP_FIXED
was specified without also specifying
-.BR MREMAP_MAYMOVE .
+.BR MREMAP_MAYMOVE ;
+or \fIold_size\fP was zero and \fIold_address\fP does not refer to a
+private anonymous mapping;
+or \fIold_size\fP was zero and the
+.BR MREMAP_MAYMOVE
+flag was not specified.
.TP
.B ENOMEM
The memory area cannot be expanded at the current virtual address, and the
@@ -210,6 +230,7 @@ if the area cannot be populated.
.BR brk (2),
.BR getpagesize (2),
.BR getrlimit (2),
+.BR memfd_create(2),
.BR mlock (2),
.BR mmap (2),
.BR sbrk (2),
--
2.13.5
next reply other threads:[~2017-09-15 21:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 21:37 Mike Kravetz [this message]
2017-09-15 21:53 ` Mike Kravetz
2017-09-18 13:45 ` Florian Weimer
2017-09-18 17:11 ` Mike Kravetz
2017-09-19 12:11 ` Florian Weimer
2017-09-19 21:42 ` [patch v2] " Mike Kravetz
2017-09-20 7:25 ` Michael Kerrisk (man-pages)
2017-09-25 12:36 ` Michal Hocko
2017-09-25 12:40 ` Michael Kerrisk (man-pages)
2017-09-25 16:33 ` Mike Kravetz
2017-09-25 19:26 ` Michael Kerrisk (man-pages)
2017-09-25 12:35 ` [patch] " Michal Hocko
2017-09-25 12:40 ` Florian Weimer
2017-09-25 12:52 ` Michal Hocko
2017-09-25 13:16 ` Florian Weimer
2017-09-25 14:52 ` Michal Hocko
2017-09-25 14:54 ` Florian Weimer
2017-09-18 1:52 ` Jann Horn
2017-09-18 17:19 ` Mike Kravetz
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=20170915213745.6821-1-mike.kravetz@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=aarcange@redhat.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mtk.manpages@gmail.com \
--cc=vbabka@suse.cz \
/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®