This was introduced with upstream stress-ng commit:

commit f954db3afe8ae2dc9474908250d3a2c595200a94
Author: Colin Ian King <>
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 <>

..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

I've fixed this with upstream fix:

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 Kernel
Packages, which is subscribed to linux in Ubuntu.

  "vforkmany" test in the smoke test test suite will stuck on Xenial

Status in stress-ng package in Ubuntu:
  Fix Committed

Bug description:
  I tried it twice on our node "gonzo" for regression-testing, but it
  always stuck on the same task  (over 1 day)

  ERROR - 06:10:35 DEBUG| [stdout] urandom RETURNED 0
  ERROR - 06:10:35 DEBUG| [stdout] urandom PASSED
  ERROR - 06:10:35 DEBUG| [stdout] userfaultfd STARTING
  ERROR - 06:10:45 DEBUG| [stdout] userfaultfd RETURNED 0
  ERROR - 06:10:45 DEBUG| [stdout] userfaultfd PASSED
  ERROR - 06:10:45 DEBUG| [stdout] utime STARTING
  ERROR - 06:10:55 DEBUG| [stdout] utime RETURNED 0
  ERROR - 06:10:55 DEBUG| [stdout] utime PASSED
  ERROR - 06:10:55 DEBUG| [stdout] vfork STARTING
  ERROR - 06:11:05 DEBUG| [stdout] vfork RETURNED 0
  ERROR - 06:11:05 DEBUG| [stdout] vfork PASSED
  ERROR - 06:11:05 DEBUG| [stdout] vforkmany STARTING
  ERROR - Killed
  ERROR - 
  ERROR - Due to the above error(s), this script is unable to continue and is 

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to