I managed to corner the bug, the termination signal on timeout was
killing the contention process with SIGKILL and this was killing the
bogo-op increment mid increment causing the internal state to be
inconsistent on the bogo-op counter. I've pushed a fix to the main repo:
commit efb0ad344e735986b29e0e1d68454edf9d793ee4 (HEAD -> master)
Author: Colin Ian King <colin.i.k...@gmail.com>
Date: Fri Feb 3 17:36:09 2023 +0000
stress-lock{a|f|ofd}: terminate contention process with SIGALRM
This will be included in the next stress-ng release at the end of this month.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999731
Title:
disk stress test failing with code 7
Status in Stress-ng:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in stress-ng package in Ubuntu:
In Progress
Bug description:
Since mid of November we see lots of disk stress test failing with
multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them
are with lockofd stressor and system are still alive after stress
test.
05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds...
** stress-ng exited with code 7
To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1999731/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
