When the following options are enabled in the kernel build, the lock_toture test fails.
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_RWSEMS=y
It appears that the test failure is due to the difference in the dmesg output when the debug options are enabled.
When the following options are enabled in the kernel build, the lock_toture test fails. CONFIG_DEBUG_RT_MUTEXES=y CONFIG_DEBUG_SPINLOCK=y CONFIG_DEBUG_MUTEXES=y CONFIG_DEBUG_RWSEMS=y It appears that the test failure is due to the difference in the dmesg output when the debug options are enabled.
Debug options disabled: [ 7467.988164] spin_lock-torture:--- End of test: SUCCESS: nwriters_stress=32 nreaders_stress= 0 nested_locks=0 stat_interval=60 verbose=1 shuffle_interval=3 stutter=5 shutdown_secs=0 onoff _interval=0 onoff_holdoff=0
Debug options enabled: [10057.619276] spin_lock-torture:--- End of test: SUCCESS [debug]: nwriters_stress=32 nreaders_stress=0 nested_locks=0 stat_interval=60 verbose=1 shuffle_interval=3 stutter=5 shutdown_secs=0 onoff_interval=0 onoff_holdoff=0