From: Thierry Reding <thierry.reding@gmail.com>
To: Shuah Khan <shuahkh@osg.samsung.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Eric B Munson <emunson@akamai.com>,
Andrea Arcangeli <aarcange@redhat.com>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/4] selftests: vm: Ensure the mlock2 syscall number can be found
Date: Fri, 7 Aug 2015 15:44:13 +0200 [thread overview]
Message-ID: <1438955055-587-2-git-send-email-thierry.reding@gmail.com> (raw)
In-Reply-To: <1438955055-587-1-git-send-email-thierry.reding@gmail.com>
From: Thierry Reding <treding@nvidia.com>
Include the syscall.h header to ensure that the mlock2 syscall number is
available. Otherwise the test program will always return ENOSYS from the
mlock2() implementation.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
tools/testing/selftests/vm/mlock2-tests.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/vm/mlock2-tests.c b/tools/testing/selftests/vm/mlock2-tests.c
index 11c38e96f336..2949fd949973 100644
--- a/tools/testing/selftests/vm/mlock2-tests.c
+++ b/tools/testing/selftests/vm/mlock2-tests.c
@@ -6,6 +6,7 @@
#include <string.h>
#include <sys/time.h>
#include <sys/resource.h>
+#include <syscall.h>
#include <errno.h>
#include <stdbool.h>
--
2.4.5
next prev parent reply other threads:[~2015-08-07 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 13:44 [PATCH 1/4] selftests: vm: Fix mlock2-tests for 32-bit architectures Thierry Reding
2015-08-07 13:44 ` Thierry Reding [this message]
2015-08-07 13:44 ` [PATCH 3/4] selftests: vm: Use the right arguments for main() Thierry Reding
2015-08-07 13:44 ` [PATCH 4/4] selftests: vm: Pick up sanitized kernel headers Thierry Reding
2015-08-10 19:27 ` [PATCH 1/4] selftests: vm: Fix mlock2-tests for 32-bit architectures Shuah Khan
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=1438955055-587-2-git-send-email-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=emunson@akamai.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkh@osg.samsung.com \
/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®