From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: IGT development <igt-dev@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>
Subject: [igt-dev] [PATCH i-g-t 5/7] lib: Make sure we leak no child processes
Date: Thu, 7 Feb 2019 17:50:58 +0100 [thread overview]
Message-ID: <20190207165100.20407-5-daniel.vetter@ffwll.ch> (raw)
In-Reply-To: <20190207165100.20407-1-daniel.vetter@ffwll.ch>
There's a lot more ways to leak children than igt_fork, some even
handrolled. So check for that. Also have a nice littel testcase for
that too.
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
---
lib/igt_core.c | 4 ++++
lib/tests/igt_fork.c | 18 ++++++++++++++++++
2 files changed, 22 insertions(+)
diff --git a/lib/igt_core.c b/lib/igt_core.c
index a23e29ca36fe..7329a85b69bf 100644
--- a/lib/igt_core.c
+++ b/lib/igt_core.c
@@ -1492,6 +1492,8 @@ void __igt_fail_assert(const char *domain, const char *file, const int line,
*/
void igt_exit(void)
{
+ int tmp;
+
igt_exit_called = true;
if (igt_key_file)
@@ -1527,6 +1529,8 @@ void igt_exit(void)
kill(test_children[c], SIGKILL);
assert(!num_test_children);
+ assert(wait(&tmp) == -1 && errno == ECHILD);
+
if (!test_with_subtests) {
struct timespec now;
const char *result;
diff --git a/lib/tests/igt_fork.c b/lib/tests/igt_fork.c
index e5b0ab016b23..b486d07000bb 100644
--- a/lib/tests/igt_fork.c
+++ b/lib/tests/igt_fork.c
@@ -68,6 +68,20 @@ static void igt_fork_leak(void)
}
}
+static void plain_fork_leak(void)
+{
+ int pid;
+
+ switch (pid = fork()) {
+ case -1:
+ internal_assert(0);
+ case 0:
+ sleep(1);
+ default:
+ exit(0);
+ }
+}
+
static void igt_fork_timeout_leak(void)
{
igt_fork(i, 1) {
@@ -122,4 +136,8 @@ int main(int argc, char **argv)
/* check that igt_waitchildren_timeout cleans up*/
ret = do_fork(igt_fork_timeout_leak);
internal_assert(ret == IGT_EXIT_FAILURE);
+
+ /* check that any other process leaks are caught*/
+ ret = do_fork(plain_fork_leak);
+ internal_assert(ret == SIGABRT + 128);
}
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-07 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 16:50 [igt-dev] [PATCH i-g-t 1/7] lib/tests: Check that igt_assert forwards correctly through igt_fork Daniel Vetter
2019-02-07 16:50 ` [igt-dev] [PATCH i-g-t 2/7] lib/tests: make sure igt_skip in igt_fork is forbidden Daniel Vetter
2019-02-07 16:50 ` [igt-dev] [PATCH i-g-t 3/7] lib: Don't leak children in igt_waitchildren_timeout Daniel Vetter
2019-02-07 16:50 ` [igt-dev] [PATCH i-g-t 4/7] lib/tests: make sure we catch igt_fork leaks Daniel Vetter
2019-02-07 16:50 ` Daniel Vetter [this message]
2019-02-07 16:50 ` [igt-dev] [PATCH i-g-t 6/7] lib: Drop igt_child_done Daniel Vetter
2019-02-07 16:51 ` [igt-dev] [PATCH i-g-t 7/7] lib: Drop IGT_EXIT_TIMEOUT Daniel Vetter
2019-02-07 17:10 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/7] lib/tests: Check that igt_assert forwards correctly through igt_fork Patchwork
2019-02-07 18:44 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=20190207165100.20407-5-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@lists.freedesktop.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