This was introduced with upstream stress-ng commit:
commit f954db3afe8ae2dc9474908250d3a2c595200a94
Author: Colin Ian King <[email protected]>
Date: Wed Jun 7 20:01:16 2017 +0100
stress-vforkmany: remove as many calls as possible
We should remove as many function calls so we don't clobber the stack.
Signed-off-by: Colin Ian King <[email protected]>
..the code added a wrapper process to ensure that kill'd vfork children
were respawned, however, the non-OOM-able setting on the vfork processes
were causing the OOM killer to reap everything except the vfork
children.
I've fixed this with upstream fix:
http://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=5f3c93335def9985d479e891f3eb5939c1dd3797
This now makes vfork processes OOM-able by default.
** Package changed: linux (Ubuntu) => stress-ng (Ubuntu)
** Changed in: stress-ng (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698747
Title:
"vforkmany" test in the smoke test test suite will stuck on Xenial
i386
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1698747/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
