[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1440787372-30214-1-git-send-email-emunson@akamai.com>
Date: Fri, 28 Aug 2015 14:42:52 -0400
From: Eric B Munson <emunson@...mai.com>
To: mtk.manpages@...il.com
Cc: Eric B Munson <emunson@...mai.com>, Michal Hocko <mhocko@...e.cz>,
David Rientjes <rientjes@...gle.com>,
linux-man@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: [PATCH] mremap.2: Add note about mremap with locked areas
When mremap() is used to move or expand a mapping that is locked with
mlock() or equivalent it will attempt to populate the new area.
However, like mmap(MAP_LOCKED), mremap() will not fail if the area
cannot be populated. Also like mmap(MAP_LOCKED) this might come as a
surprise to users and should be noted.
Signed-off-by: Eric B Munson <emunson@...mai.com>
Cc: Michal Hocko <mhocko@...e.cz>
Cc: David Rientjes <rientjes@...gle.com>
Cc: linux-man@...r.kernel.org
Cc: linux-mm@...ck.org
Cc: linux-kernel@...r.kernel.org
---
man2/mremap.2 | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/man2/mremap.2 b/man2/mremap.2
index 071adb5..cf884e6 100644
--- a/man2/mremap.2
+++ b/man2/mremap.2
@@ -196,6 +196,17 @@ and the prototype for
did not allow for the
.I new_address
argument.
+
+If
+.BR mremap ()
+is used to move or expand an area locked with
+.BR mlock (2)
+or equivalent, the
+.BR mremap ()
+call will make a best effort to populate the new area but will not fail
+with
+.B ENOMEM
+if the area cannot be populated.
.SH SEE ALSO
.BR brk (2),
.BR getpagesize (2),
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists