From: Steve Muckle <smuckle.linux@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/keyctl07: skip test if syscall unavailable
Date: Thu, 1 Feb 2018 11:07:33 -0800 [thread overview]
Message-ID: <20180201190733.6935-1-smuckle.linux@gmail.com> (raw)
If the child is unable to run the test because the syscall is
unavailable TBROK is currently reported. Look for TCONF from the
child and report that in this scenario instead.
Signed-off-by: Steve Muckle <smuckle.linux@gmail.com>
---
testcases/kernel/syscalls/keyctl/keyctl07.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/testcases/kernel/syscalls/keyctl/keyctl07.c b/testcases/kernel/syscalls/keyctl/keyctl07.c
index 39f07eb5fbce..08a585b6c956 100644
--- a/testcases/kernel/syscalls/keyctl/keyctl07.c
+++ b/testcases/kernel/syscalls/keyctl/keyctl07.c
@@ -106,6 +106,9 @@ static void do_test(void)
return;
}
+ if (WIFEXITED(status) && WEXITSTATUS(status) == TCONF)
+ tst_brk(TCONF, "syscall not implemented");
+
tst_brk(TBROK, "Child %s", tst_strstatus(status));
}
--
2.13.6
next reply other threads:[~2018-02-01 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 19:07 Steve Muckle [this message]
2018-02-06 11:41 ` [LTP] [PATCH] syscalls/keyctl07: skip test if syscall unavailable Petr Vorel
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=20180201190733.6935-1-smuckle.linux@gmail.com \
--to=smuckle.linux@gmail.com \
--cc=ltp@lists.linux.it \
/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