From: Cyril Hrubis <chrubis@suse.cz>
To: "Ricardo B. Marlière" <ricardo@marliere.net>
Cc: "Ricardo B. Marlière" <rbm@suse.com>,
"Linux Test Project" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2 2/3] syscalls/pause02: Refactor into new API
Date: Fri, 21 Feb 2025 11:39:38 +0100 [thread overview]
Message-ID: <Z7hX6iJN6hDSUgUZ@yuki.lan> (raw)
In-Reply-To: <20250218-conversions-pause-v2-2-8c72960fe1ec@suse.com>
Hi!
This is the same as pause01.c there is no point in having two tests that
do the same.
So rather than rewriting this test we should add a check to the
pause01.c that the process resumed after the signal. Which should be as
easy as:
diff --git a/testcases/kernel/syscalls/pause/pause01.c b/testcases/kernel/syscalls/pause/pause01.c
index adce0ddcf..74a7e514e 100644
--- a/testcases/kernel/syscalls/pause/pause01.c
+++ b/testcases/kernel/syscalls/pause/pause01.c
@@ -20,6 +20,8 @@ static void do_child(void)
SAFE_SIGNAL(SIGINT, sig_handler);
TST_EXP_FAIL(pause(), EINTR);
TST_CHECKPOINT_WAKE(0);
+
+ tst_res(TPASS, "Process resumed from pause()");
}
And it would also make sense to add more coverage to pause01 in a
subsequent patch. Currently it tests only a single signal, we should
iterate over all signals instead (minus the SIGKILL that is covered by
pause03).
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-02-21 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 18:07 [LTP] [PATCH v2 0/3] syscalls/pause: Refactor tests Ricardo B. Marlière
2025-02-18 18:07 ` [LTP] [PATCH v2 1/3] syscalls/pause01: Clean up Ricardo B. Marlière
2025-02-21 10:17 ` Cyril Hrubis
2025-02-18 18:07 ` [LTP] [PATCH v2 2/3] syscalls/pause02: Refactor into new API Ricardo B. Marlière
2025-02-21 10:39 ` Cyril Hrubis [this message]
2025-02-24 10:49 ` Ricardo B. Marlière via ltp
2025-02-18 18:07 ` [LTP] [PATCH v2 3/3] syscalls/pause03: " Ricardo B. Marlière
2025-02-21 10:32 ` Cyril Hrubis
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=Z7hX6iJN6hDSUgUZ@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rbm@suse.com \
--cc=ricardo@marliere.net \
/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.