Lines Matching full:is

10 debugobjects is a generic infrastructure to track the life time of
13 debugobjects is useful to check for the following error patterns:
21 debugobjects is not changing the data structure of the real object so it
56 Each detected error is reported in the statistics and a limited number
70 This function is called whenever the initialization function of a real
71 object is called.
73 When the real object is already tracked by debugobjects it is checked,
74 whether the object can be initialized. Initializing is not allowed for
82 When the real object is not yet tracked by debugobjects, debugobjects
84 object state to ODEBUG_STATE_INIT. It verifies that the object is not
85 on the callers stack. If it is on the callers stack then a limited
86 number of warnings including a full stack trace is printk'ed. The
93 This function is called whenever the initialization function of a real
94 object which resides on the stack is called.
96 When the real object is already tracked by debugobjects it is checked,
97 whether the object can be initialized. Initializing is not allowed for
105 When the real object is not yet tracked by debugobjects debugobjects
107 object state to ODEBUG_STATE_INIT. It verifies that the object is on
110 An object which is on the stack must be removed from the tracker by
117 This function is called whenever the activation function of a real
118 object is called.
120 When the real object is already tracked by debugobjects it is checked,
121 whether the object can be activated. Activating is not allowed for
128 When the real object is not yet tracked by debugobjects then the
129 fixup_activate function is called if available. This is necessary to
131 objects. The fixup function checks whether the object is valid and calls
135 When the activation is legitimate, then the state of the associated
136 tracker object is set to ODEBUG_STATE_ACTIVE.
142 This function is called whenever the deactivation function of a real
143 object is called.
145 When the real object is tracked by debugobjects it is checked, whether
146 the object can be deactivated. Deactivating is not allowed for untracked
149 When the deactivation is legitimate, then the state of the associated
150 tracker object is set to ODEBUG_STATE_INACTIVE.
155 This function is called to mark an object destroyed. This is useful to
160 When the real object is tracked by debugobjects it is checked, whether
161 the object can be destroyed. Destruction is not allowed for active and
168 When the destruction is legitimate, then the state of the associated
169 tracker object is set to ODEBUG_STATE_DESTROYED.
174 This function is called before an object is freed.
176 When the real object is tracked by debugobjects it is checked, whether
177 the object can be freed. Free is not allowed for active objects. When
185 usage of the object is detected by the other debug checks.
191 This function is called to assert that an object has been initialized.
193 When the real object is not tracked by debugobjects, it calls
199 When the real object is already tracked by debugobjects it is ignored.
213 This function is called from the debug code whenever a problem in
214 debug_object_init is detected. The function takes the address of the
215 object and the state which is currently recorded in the tracker.
217 Called from debug_object_init when the object state is:
222 false. The return value is used to update the statistics.
231 This function is called from the debug code whenever a problem in
232 debug_object_activate is detected.
234 Called from debug_object_activate when the object state is:
241 false. The return value is used to update the statistics.
247 The activation of statically initialized objects is a special case. When
249 then fixup_activate() is called with object state
251 this is a legitimate case of a statically initialized object or not. In
252 case it is it calls debug_object_init() and debug_object_activate()
254 the function should return false because this is not a real fixup.
259 This function is called from the debug code whenever a problem in
260 debug_object_destroy is detected.
262 Called from debug_object_destroy when the object state is:
267 false. The return value is used to update the statistics.
272 This function is called from the debug code whenever a problem in
273 debug_object_free is detected. Further it can be called from the debug
274 checks in kfree/vfree, when an active object is detected from the
278 the object state is:
283 false. The return value is used to update the statistics.
288 This function is called from the debug code whenever a problem in
289 debug_object_assert_init is detected.
292 ODEBUG_STATE_NOTAVAILABLE when the object is not found in the debug
296 false. The return value is used to update the statistics.
298 Note, this function should make sure debug_object_init() is called
301 The handling of statically initialized objects is a special case. The
302 fixup function should check if this is a legitimate case of a statically
305 function should return false because this is not a real fixup.