obj_sync/TEST0 timeout under pmemcheck

[grom72]

ISSUE: obj_sync/TEST0 timeout under pmemcheck

Environment Information

• PMDK package version(s): 37292d4
• OS(es) version(s): Rocky Linux 9.1 (Blue Onyx)
• ndctl version(s): 71.1
• kernel version(s): 5.14.0-162.6.1.el9_1.x86_64

Please provide a reproduction of the bug:

obj_sync/TEST0 timeout under valgrind (self-hosted, rhel, RUNTESTS -p force-enable)

https://github.com/pmem/pmdk/actions/runs/4961833388/jobs/8894945681#step:6:4612

How often bug is revealed: (always, often, rare):

Actual behavior:

obj_sync/TEST0: SETUP (check/none/debug/pmemcheck)
RUNTESTS: stopping: obj_sync/TEST0 timed out, TEST=check FS=none BUILD=debug

Expected behavior:

Details

Additional information about Priority and Help Requested:

Are you willing to submit a pull request with a proposed change? (Yes, No)

Requested priority: (Showstopper, High, Medium, Low)

[grom72]

Very short test.

[tgromadz@wp162 test]$ ./RUNTESTS -t check -p force-enable -u 0 obj_sync
obj_sync/TEST0: SETUP (check/none/debug/pmemcheck)
obj_sync/TEST0: START: obj_sync
 ./obj_sync m 50 5
{obj_sync.c:65 mutex_write_worker} obj_sync/TEST0: pmemobj_mutex_lock
obj_sync/TEST0: DONE
obj_sync/TEST0: PASS                    [00.515 s]
obj_sync/TEST0: SETUP (check/none/nondebug/pmemcheck)
obj_sync/TEST0: START: obj_sync
 ./obj_sync m 50 5
{obj_sync.c:85 mutex_check_worker} obj_sync/TEST0: pmemobj_mutex_lock
obj_sync/TEST0: DONE
obj_sync/TEST0: PASS                    [00.506 s]

Timeout means something wrong has happened.