oom'd processes with --oomable option don't copy back bogo-ops stats because of an _exit() in core-out-of-memory.c

Bug #1879696 reported by Colin Ian King
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
stress-ng (Ubuntu)
Fix Released
High
Colin Ian King

Bug Description

stress_oomable_child() calls _exit in the child rather than a return, causing the post stressor stats not to be copied over and triggering a corrupted bogo ops report. Fix this by returning EXIT_NO_RESOURCE rather than _exit()

Changed in stress-ng (Ubuntu):
importance: Undecided → High
status: New → In Progress
assignee: nobody → Colin Ian King (colin-king)
Revision history for this message
Colin Ian King (colin-king) wrote :
Changed in stress-ng (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package stress-ng - 0.11.12-1

---------------
stress-ng (0.11.12-1) unstable; urgency=medium

  * Makefile: bump minor version
  * Setup the checksum before forking off child stressor (LP: #1880840)
    - fixes null checksum if child is killed before the stressor
      function gets invoked.

 -- Colin King <email address hidden> Wed, 27 May 2020 09:53:11 +0100

Changed in stress-ng (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.