From: Hu Yadi <hu.yadi@h3c.com>
To: <jmorris@namei.org>, <serge@hallyn.com>, <shuah@kernel.org>,
<mathieu.desnoyers@efficios.com>, <mic@digikod.net>
Cc: <linux-api@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-security-module@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <514118380@qq.com>,
<jiaoxupo@h3c.com>, "Hu.Yadi" <hu.yadi@h3c.com>
Subject: [PATCH] selftests/core: Fix build issue with CLOSE_RANGE_UNSHARE
Date: Thu, 11 Jan 2024 11:47:47 +0800 [thread overview]
Message-ID: <20240111034747.39746-1-hu.yadi@h3c.com> (raw)
From: "Hu.Yadi" <hu.yadi@h3c.com>
Add head file to fix cpmpile error:
gcc -g -isystem /home/linux/usr/include close_range_test.c -o /home/linux/tools/testing/selftests/core/close_range_test
close_range_test.c: In function ‘close_range_unshare’:
close_range_test.c:111:11: error: ‘CLOSE_RANGE_UNSHARE’ undeclared (first use in this function); did you mean ‘CLONE_NEWUSER’?
CLOSE_RANGE_UNSHARE);
^~~~~~~~~~~~~~~~~~~
Signed-off-by: Hu.Yadi <hu.yadi@h3c.com>
Suggested-by: Jiao <jiaoxupo@h3c.com>
Reviewed-by: Berlin <berlin@h3c.com>
---
tools/testing/selftests/core/close_range_test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/core/close_range_test.c b/tools/testing/selftests/core/close_range_test.c
index 534576f06df1..563bc1e55937 100644
--- a/tools/testing/selftests/core/close_range_test.c
+++ b/tools/testing/selftests/core/close_range_test.c
@@ -12,7 +12,7 @@
#include <syscall.h>
#include <unistd.h>
#include <sys/resource.h>
-
+#include <linux/close_range.h>
#include "../kselftest_harness.h"
#include "../clone3/clone3_selftests.h"
--
2.23.0
next reply other threads:[~2024-01-11 3:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 3:47 Hu Yadi [this message]
2024-01-12 5:24 ` 回复: [PATCH] selftests/core: Fix build issue with CLOSE_RANGE_UNSHARE Huyadi
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=20240111034747.39746-1-hu.yadi@h3c.com \
--to=hu.yadi@h3c.com \
--cc=514118380@qq.com \
--cc=jiaoxupo@h3c.com \
--cc=jmorris@namei.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mic@digikod.net \
--cc=serge@hallyn.com \
--cc=shuah@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).