From: Matthias Maennich <maennich@google.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 0/2] sigpending / rt_sigpending
Date: Tue, 12 Feb 2019 16:12:34 +0000 [thread overview]
Message-ID: <20190212161236.74385-1-maennich@google.com> (raw)
In-Reply-To: <20190207155153.41816-1-maennich@google.com>
Split the `sigpending` test case into rt_sigpending and sigpending, both
bypassing any syscall wrappers.
Obviously these tests are currently only testing a rare corner case and
more thorough testing is needed to cover both of the syscalls. That work
is to be done in a later commit.
Matthias Maennich (2):
sigpending: use direct syscall
rt_sigpending: add rt_sigpending02 test case
runtest/syscalls | 1 +
.../kernel/syscalls/rt_sigpending/.gitignore | 1 +
.../kernel/syscalls/rt_sigpending/Makefile | 23 +++++++++
.../syscalls/rt_sigpending/rt_sigpending02.c | 48 +++++++++++++++++++
.../kernel/syscalls/sigpending/sigpending02.c | 3 +-
5 files changed, 75 insertions(+), 1 deletion(-)
create mode 100644 testcases/kernel/syscalls/rt_sigpending/.gitignore
create mode 100644 testcases/kernel/syscalls/rt_sigpending/Makefile
create mode 100644 testcases/kernel/syscalls/rt_sigpending/rt_sigpending02.c
--
2.20.1.791.gb4d0f1c61a-goog
next prev parent reply other threads:[~2019-02-12 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 15:51 [LTP] [PATCH v1] sigpending: use direct syscall Matthias Maennich
2019-02-07 18:58 ` Steve Muckle
2019-02-11 8:28 ` Matthias =?unknown-8bit?q?M=C3=A4nnich?=
2019-02-12 16:12 ` Matthias Maennich [this message]
2019-02-12 16:12 ` [LTP] [PATCH v2 1/2] " 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=20190212161236.74385-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.