From: wei.guo.simon@gmail.com
To: linux-mm@kvack.org
Cc: Alexey Klimov <klimov.linux@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Eric B Munson <emunson@akamai.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
Simon Guo <wei.guo.simon@gmail.com>,
Thierry Reding <treding@nvidia.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: [PATCH 4/4] selftests/vm: add test for mlock() when areas are intersected.
Date: Tue, 30 Aug 2016 18:59:41 +0800 [thread overview]
Message-ID: <1472554781-9835-5-git-send-email-wei.guo.simon@gmail.com> (raw)
In-Reply-To: <1472554781-9835-1-git-send-email-wei.guo.simon@gmail.com>
From: Simon Guo <wei.guo.simon@gmail.com>
This patch adds mlock() test for multiple invocation on
the same address area, and verify it doesn't mess the
rlimit mlock limitation.
Signed-off-by: Simon Guo <wei.guo.simon@gmail.com>
---
tools/testing/selftests/vm/.gitignore | 1 +
tools/testing/selftests/vm/Makefile | 4 ++
tools/testing/selftests/vm/mlock-intersect-test.c | 76 +++++++++++++++++++++++
3 files changed, 81 insertions(+)
create mode 100644 tools/testing/selftests/vm/mlock-intersect-test.c
diff --git a/tools/testing/selftests/vm/.gitignore b/tools/testing/selftests/vm/.gitignore
index a937a9d..142c565 100644
--- a/tools/testing/selftests/vm/.gitignore
+++ b/tools/testing/selftests/vm/.gitignore
@@ -7,3 +7,4 @@ mlock2-tests
on-fault-limit
transhuge-stress
userfaultfd
+mlock-intersect-test
diff --git a/tools/testing/selftests/vm/Makefile b/tools/testing/selftests/vm/Makefile
index e4bb1de..a0412a8 100644
--- a/tools/testing/selftests/vm/Makefile
+++ b/tools/testing/selftests/vm/Makefile
@@ -10,6 +10,7 @@ BINARIES += on-fault-limit
BINARIES += thuge-gen
BINARIES += transhuge-stress
BINARIES += userfaultfd
+BINARIES += mlock-intersect-test
all: $(BINARIES)
%: %.c
@@ -17,6 +18,9 @@ all: $(BINARIES)
userfaultfd: userfaultfd.c ../../../../usr/include/linux/kernel.h
$(CC) $(CFLAGS) -O2 -o $@ $< -lpthread
+mlock-intersect-test: mlock-intersect-test.c
+ $(CC) $(CFLAGS) -o $@ $< -lcap
+
../../../../usr/include/linux/kernel.h:
make -C ../../../.. headers_install
diff --git a/tools/testing/selftests/vm/mlock-intersect-test.c b/tools/testing/selftests/vm/mlock-intersect-test.c
new file mode 100644
index 0000000..f78e68a
--- /dev/null
+++ b/tools/testing/selftests/vm/mlock-intersect-test.c
@@ -0,0 +1,76 @@
+/*
+ * It tests the duplicate mlock result:
+ * - the ulimit of lock page is 64k
+ * - allocate address area 64k starting from p
+ * - mlock [p -- p + 30k]
+ * - Then mlock address [ p -- p + 40k ]
+ *
+ * It should succeed since totally we locked
+ * 40k < 64k limitation.
+ *
+ * It should not be run with CAP_IPC_LOCK.
+ */
+#include <stdlib.h>
+#include <stdio.h>
+#include <unistd.h>
+#include <sys/resource.h>
+#include <sys/capability.h>
+#include <sys/mman.h>
+#include "mlock2.h"
+
+int main(int argc, char **argv)
+{
+ struct rlimit new;
+ char *p = NULL;
+ cap_t cap = cap_init();
+ int i;
+
+ /* drop capabilities including CAP_IPC_LOCK */
+ if (cap_set_proc(cap))
+ return -1;
+
+ /* set mlock limits to 64k */
+ new.rlim_cur = 65536;
+ new.rlim_max = 65536;
+ setrlimit(RLIMIT_MEMLOCK, &new);
+
+ /* test VM_LOCK */
+ p = malloc(1024 * 64);
+ if (mlock(p, 1024 * 30)) {
+ printf("mlock() 30k return failure.\n");
+ return -1;
+ }
+ for (i = 0; i < 10; i++) {
+ if (mlock(p, 1024 * 40)) {
+ printf("mlock() #%d 40k returns failure.\n", i);
+ return -1;
+ }
+ }
+ for (i = 0; i < 10; i++) {
+ if (mlock2_(p, 1024 * 40, MLOCK_ONFAULT)) {
+ printf("mlock2_() #%d 40k returns failure.\n", i);
+ return -1;
+ }
+ }
+ free(p);
+
+ /* Test VM_LOCKONFAULT */
+ p = malloc(1024 * 64);
+ if (mlock2_(p, 1024 * 30, MLOCK_ONFAULT)) {
+ printf("mlock2_() 30k return failure.\n");
+ return -1;
+ }
+ for (i = 0; i < 10; i++) {
+ if (mlock2_(p, 1024 * 40, MLOCK_ONFAULT)) {
+ printf("mlock2_() #%d 40k returns failure.\n", i);
+ return -1;
+ }
+ }
+ for (i = 0; i < 10; i++) {
+ if (mlock(p, 1024 * 40)) {
+ printf("mlock() #%d 40k returns failure.\n", i);
+ return -1;
+ }
+ }
+ return 0;
+}
--
1.8.3.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-08-30 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 10:59 [PATCH 0/4] mm: mlock: fix some locked_vm counting issues wei.guo.simon
2016-08-30 10:59 ` [PATCH 1/4] mm: mlock: check against vma for actual mlock() size wei.guo.simon
2016-08-30 11:35 ` Kirill A. Shutemov
2016-08-30 10:59 ` [PATCH 2/4] mm: mlock: avoid increase mm->locked_vm on mlock() when already mlock2(,MLOCK_ONFAULT) wei.guo.simon
2016-08-30 11:36 ` Kirill A. Shutemov
2016-08-30 10:59 ` [PATCH 3/4] selftest: split mlock2_ funcs into separate mlock2.h wei.guo.simon
2016-08-30 10:59 ` wei.guo.simon [this message]
2016-08-31 23:14 ` [PATCH 4/4] selftests/vm: add test for mlock() when areas are intersected David Rientjes
2016-09-01 7:14 ` Simon Guo
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=1472554781-9835-5-git-send-email-wei.guo.simon@gmail.com \
--to=wei.guo.simon@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=emunson@akamai.com \
--cc=geert@linux-m68k.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=klimov.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=shuah@kernel.org \
--cc=treding@nvidia.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