Home
last modified time | relevance | path

Searched refs:validator (Results 1 – 7 of 7) sorted by relevance

/Linux-v4.19/drivers/md/persistent-data/
Ddm-block-manager.c347 struct dm_block_validator *validator; member
358 aux->validator = NULL; in dm_block_manager_alloc_callback()
365 if (aux->validator) { in dm_block_manager_write_callback()
366 aux->validator->prepare_for_write(aux->validator, (struct dm_block *) buf, in dm_block_manager_write_callback()
434 if (unlikely(!aux->validator)) { in dm_bm_validate_buffer()
444 aux->validator = v; in dm_bm_validate_buffer()
446 if (unlikely(aux->validator != v)) { in dm_bm_validate_buffer()
448 aux->validator->name, v ? v->name : "NULL", in dm_bm_validate_buffer()
583 aux->validator = v; in dm_bm_write_lock_zero()
/Linux-v4.19/Documentation/locking/
Dlockdep-design.txt1 Runtime locking correctness validator
10 The basic object the validator operates upon is a 'class' of locks.
18 The validator tracks the 'state' of lock-classes, and it tracks
19 dependencies between different lock-classes. The validator maintains a
30 The validator tracks lock-class usage history into 4 * nSTATEs + 1 separate
75 The validator detects and reports lock usage that violate these
89 because this could lead to lock inversion deadlocks. (The validator
92 validator will still track all dependencies between locks.)
107 kernel: when acquiring a new lock, the validator checks whether there is
144 lock, the lock ordering is fully correct. The validator does not
[all …]
D00-INDEX4 - documentation on the runtime locking correctness validator.
/Linux-v4.19/Documentation/gpu/
Dvc4.rst72 :doc: Command list validator for VC4.
80 Shader validator for VC4
83 :doc: Shader validator for VC4.
/Linux-v4.19/sound/usb/
Dclock.c39 bool (*validator)(void *, int), u8 type) in find_uac_clock_desc()
45 if (validator(cs, id)) in find_uac_clock_desc()
90 #define DEFINE_FIND_HELPER(name, obj, validator, type) \ argument
93 return find_uac_clock_desc(iface, id, validator, type); \
/Linux-v4.19/Documentation/
Dirqflags-tracing.txt33 trace_hardirqs_off()/trace_hardirqs_on() functions. The lock validator
48 turn itself off. I.e. the lock validator will still be reliable. There
/Linux-v4.19/Documentation/filesystems/
Daffs.txt210 no way to fix a garbled filesystem without an Amiga (disk validator)