Searched refs:validator (Results 1 – 5 of 5) sorted by relevance
1 Runtime locking correctness validator10 The basic object the validator operates upon is a 'class' of locks.18 The validator tracks the 'state' of lock-classes, and it tracks19 dependencies between different lock-classes. The validator maintains a30 The validator tracks lock-class usage history into 4n + 1 separate state bits:75 The validator detects and reports lock usage that violate these89 because this could lead to lock inversion deadlocks. (The validator92 validator will still track all dependencies between locks.)107 kernel: when acquiring a new lock, the validator checks whether there is144 lock, the lock ordering is fully correct. The validator does not[all …]
4 - documentation on the runtime locking correctness validator.
341 struct dm_block_validator *validator; member349 aux->validator = NULL; in dm_block_manager_alloc_callback()356 if (aux->validator) { in dm_block_manager_write_callback()357 aux->validator->prepare_for_write(aux->validator, (struct dm_block *) buf, in dm_block_manager_write_callback()426 if (unlikely(!aux->validator)) { in dm_bm_validate_buffer()436 aux->validator = v; in dm_bm_validate_buffer()438 if (unlikely(aux->validator != v)) { in dm_bm_validate_buffer()440 aux->validator->name, v ? v->name : "NULL", in dm_bm_validate_buffer()575 aux->validator = v; in dm_bm_write_lock_zero()
31 trace_hardirqs_off()/trace_hardirqs_on() functions. The lock validator46 turn itself off. I.e. the lock validator will still be reliable. There
210 no way to fix a garbled filesystem without an Amiga (disk validator)