flock stress test exits with code 7

Bug #2016966 reported by Ike Panhc
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Stress-ng
Triaged
High
Colin Ian King

Bug Description

Just as bug 1999731 and we have similiar problem with flock stressor and sometimes (<10%) it exits with return value 7.

$ ./stress-ng --flock 0 -t 240
stress-ng: info: [43524] setting to a 240 second (4 mins, 0.00 secs) run per stressor
stress-ng: info: [43524] dispatching hogs: 48 flock
stress-ng: warn: [43617] flock: WARNING: bogo-ops counter in non-ready state, metrics are untrustworthy (process may have been terminated prematurely)
stress-ng: info: [43524] passed: 47: flock (47)
stress-ng: info: [43524] failed: 1: flock (1)
stress-ng: info: [43524] skipped: 0
stress-ng: info: [43524] successful run completed in 240.14s (4 mins, 0.14 secs)
$ echo $?
7

Revision history for this message
Ike Panhc (ikepanhc) wrote :

Here is the suggested fix. I have applied this patch on stress-ng commit c3d4a218 and it passes 300 times flock stress run.

Revision history for this message
Colin Ian King (colin-king) wrote :

This has been fixed for various stressors with upstream fix:

commit c0b3e366f57c7295df19989c57b6c3c8642b098a (HEAD -> master)
Author: Colin Ian King <email address hidden>
Date: Sun Apr 23 14:26:51 2023 +0100

    Add forced_killed_counter to indicate a child has been killed forcefully

Changed in stress-ng:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Colin Ian King (colin-king)
Revision history for this message
Ike Panhc (ikepanhc) wrote :

Thanks Colin,

I have test HEAD(09433fdf) last week with patch c0b3e366 and V0.15.07.

I have 0/300 and 25/300 reproduce rate on 09433fdf and V0.15.07.

I can confirm this issue is fix.

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.