From: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Michael Hebenstreit <michael.hebenstreit@intel.com>,
Petri Latvala <petri.latvala@intel.com>,
Fei Yang <fei.yang@intel.com>
Subject: [igt-dev] [PATCH i-g-t] lib/igt_core: Don't kill the world after a failed fork
Date: Wed, 3 Jun 2020 15:54:14 +0300 [thread overview]
Message-ID: <20200603125414.1027845-1-arkadiusz.hiler@intel.com> (raw)
If we fail to fork (e.g. due to restrictive limits) -1 gets written as
PID of our child and we assert out.
The cleanup that happens afterwards tries to kill all our children,
which ends up in kill(-1, SIGKILL) which is not good.
This patch makes sure of two things:
* -1 doesn't get written down as our child
* when we are killing children we make sure that pid > 0
Reported-by: Fei Yang <fei.yang@intel.com>
Cc: Michael Hebenstreit <michael.hebenstreit@intel.com>
Cc: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
---
lib/igt_core.c | 19 +++++++++++--------
lib/tests/igt_fork.c | 6 ++++--
2 files changed, 15 insertions(+), 10 deletions(-)
diff --git a/lib/igt_core.c b/lib/igt_core.c
index f8ccc8d2..cbcc3f4d 100644
--- a/lib/igt_core.c
+++ b/lib/igt_core.c
@@ -1399,8 +1399,10 @@ static void exit_subtest(const char *result)
/* If the subtest aborted, it may have left children behind */
for (int c = 0; c < num_test_children; c++) {
- kill(test_children[c], SIGKILL);
- waitpid(test_children[c], NULL, 0); /* don't leave zombies! */
+ if (test_children[c] > 0) {
+ kill(test_children[c], SIGKILL);
+ waitpid(test_children[c], NULL, 0); /* don't leave zombies! */
+ }
}
num_test_children = 0;
@@ -1986,8 +1988,10 @@ void __igt_fail_assert(const char *domain, const char *file, const int line,
static void kill_children(void)
{
- for (int c = 0; c < num_test_children; c++)
- kill(test_children[c], SIGKILL);
+ for (int c = 0; c < num_test_children; c++) {
+ if (test_children[c] > 0)
+ kill(test_children[c], SIGKILL);
+ }
}
void __igt_abort(const char *domain, const char *file, const int line,
@@ -2276,6 +2280,7 @@ bool __igt_fork(void)
switch (test_children[num_test_children++] = fork()) {
case -1:
+ num_test_children--; /* so we won't kill(-1) during cleanup */
igt_assert(0);
case 0:
test_child = true;
@@ -2335,8 +2340,7 @@ int __igt_waitchildren(void)
err = 256;
}
- for (c = 0; c < num_test_children; c++)
- kill(test_children[c], SIGKILL);
+ kill_children();
}
count++;
@@ -2370,8 +2374,7 @@ static void igt_alarm_killchildren(int signal)
{
igt_info("Timed out waiting for children\n");
- for (int c = 0; c < num_test_children; c++)
- kill(test_children[c], SIGKILL);
+ kill_children();
}
/**
diff --git a/lib/tests/igt_fork.c b/lib/tests/igt_fork.c
index 4fd0e0c8..84492b2d 100644
--- a/lib/tests/igt_fork.c
+++ b/lib/tests/igt_fork.c
@@ -123,8 +123,10 @@ static void subtest_leak(void)
}
/* We expect the exit_subtest to cleanup after the igt_fork */
- for (int i = 0; i < num_children; i++)
- assert(kill(children[i], 0) == -1 && errno == ESRCH);
+ for (int i = 0; i < num_children; i++) {
+ if (children[i] > 0)
+ assert(kill(children[i], 0) == -1 && errno == ESRCH);
+ }
munmap(children, 4096);
--
2.25.4
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-06-03 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 12:54 Arkadiusz Hiler [this message]
2020-06-03 14:55 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/igt_core: Don't kill the world after a failed fork Patchwork
2020-06-03 15:43 ` [igt-dev] [PATCH i-g-t] " Hebenstreit, Michael
2020-06-03 16:24 ` Arkadiusz Hiler
2020-06-03 16:30 ` Hebenstreit, Michael
2020-06-04 4:35 ` [igt-dev] ✓ Fi.CI.IGT: success for " Patchwork
2020-06-04 8:39 ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2020-06-04 8:48 ` [igt-dev] ✗ Fi.CI.BUILD: failure for lib/igt_core: Don't kill the world after a failed fork (rev2) 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=20200603125414.1027845-1-arkadiusz.hiler@intel.com \
--to=arkadiusz.hiler@intel.com \
--cc=fei.yang@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=michael.hebenstreit@intel.com \
--cc=petri.latvala@intel.com \
/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