All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Maennich <maennich@google.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v1] sigpending: use direct syscall
Date: Thu,  7 Feb 2019 15:51:53 +0000	[thread overview]
Message-ID: <20190207155153.41816-1-maennich@google.com> (raw)

Expand coverage to the Android platform.

Signed-off-by: Matthias Maennich <maennich@google.com>
---
 testcases/kernel/syscalls/sigpending/sigpending02.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/testcases/kernel/syscalls/sigpending/sigpending02.c b/testcases/kernel/syscalls/sigpending/sigpending02.c
index a38157ae1..ff8b59c8c 100644
--- a/testcases/kernel/syscalls/sigpending/sigpending02.c
+++ b/testcases/kernel/syscalls/sigpending/sigpending02.c
@@ -17,13 +17,14 @@
 #include <sys/types.h>
 
 #include "tst_test.h"
+#include "lapi/syscalls.h"
 
 static void run(void)
 {
 	/* set sigset to point to an invalid location */
 	sigset_t *sigset = (sigset_t *) - 1;
 
-	TEST(sigpending(sigset));
+	TEST(tst_syscall(__NR_rt_sigpending, sigset, NSIG / 8));
 
 	/* check return code */
 	if (TST_RET == -1) {
-- 
2.20.1.611.gfbb209baf1-goog


             reply	other threads:[~2019-02-07 15:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 15:51 Matthias Maennich [this message]
2019-02-07 18:58 ` [LTP] [PATCH v1] sigpending: use direct syscall Steve Muckle
2019-02-11  8:28   ` Matthias =?unknown-8bit?q?M=C3=A4nnich?=
2019-02-12 16:12 ` [LTP] [PATCH v2 0/2] sigpending / rt_sigpending Matthias Maennich
2019-02-12 16:12   ` [LTP] [PATCH v2 1/2] sigpending: use direct syscall Matthias Maennich
2019-02-15 23:47     ` Steve Muckle
2019-02-12 16:12   ` [LTP] [PATCH v2 2/2] rt_sigpending: add rt_sigpending02 test case Matthias Maennich
2019-02-16  0:01     ` Steve Muckle
2019-02-19 14:28       ` Matthias =?unknown-8bit?q?M=C3=A4nnich?=
2019-02-19 17:57         ` Steve Muckle
2019-03-01 10:41           ` 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=20190207155153.41816-1-maennich@google.com \
    --to=maennich@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.