From: Masami Hiramatsu <mhiramat@kernel.org>
To: Shuah Khan <shuah@kernel.org>
Cc: Micah Morton <mortonm@chromium.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
jaswinder.singh@linaro.org
Subject: [BUGFIX PATCH v2 3/3] selftests: safesetid: Fix Makefile to set correct test program
Date: Thu, 5 Dec 2019 21:21:16 +0900 [thread overview]
Message-ID: <157554847591.11018.5631502480695471273.stgit@devnote2> (raw)
In-Reply-To: <157554844882.11018.13436399905210284553.stgit@devnote2>
Fix Makefile to set safesetid-test.sh to TEST_PROGS instead
of non existing run_tests.sh.
Without this fix, I got following error.
----
TAP version 13
1..1
# selftests: safesetid: run_tests.sh
# Warning: file run_tests.sh is missing!
not ok 1 selftests: safesetid: run_tests.sh
----
Fixes: c67e8ec03f3f ("LSM: SafeSetID: add selftest")
Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
---
tools/testing/selftests/safesetid/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/safesetid/Makefile b/tools/testing/selftests/safesetid/Makefile
index cac42cd36a1b..fa02c4d5ec13 100644
--- a/tools/testing/selftests/safesetid/Makefile
+++ b/tools/testing/selftests/safesetid/Makefile
@@ -3,7 +3,7 @@
CFLAGS = -Wall -O2
LDLIBS = -lcap
-TEST_PROGS := run_tests.sh
+TEST_PROGS := safesetid-test.sh
TEST_GEN_FILES := safesetid-test
include ../lib.mk
next prev parent reply other threads:[~2019-12-05 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 12:20 [BUGFIX PATCH v2 0/3] selftests: safesetid: Fix some bugs in safesetid test Masami Hiramatsu
2019-12-05 12:20 ` [BUGFIX PATCH v2 1/3] selftests: safesetid: Move link library to LDLIBS Masami Hiramatsu
2019-12-05 12:21 ` [BUGFIX PATCH v2 2/3] selftests: safesetid: Check the return value of setuid/setgid Masami Hiramatsu
2019-12-05 12:21 ` Masami Hiramatsu [this message]
2019-12-05 16:40 ` [BUGFIX PATCH v2 0/3] selftests: safesetid: Fix some bugs in safesetid test Micah Morton
2019-12-05 16:44 ` shuah
2019-12-06 1:23 ` Masami Hiramatsu
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=157554847591.11018.5631502480695471273.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=jaswinder.singh@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mortonm@chromium.org \
--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