Lines Matching +full:in +full:- +full:functions

2 The object-lifetime debugging infrastructure
15 -  Activation of uninitialized objects
17 -  Initialization of active objects
19 -  Usage of freed/destroyed objects
22 can be compiled in with a minimal runtime impact and enabled on demand
31 the object type. Optional functions can and should be provided to fixup
39 -  debug_object_init
41 -  debug_object_init_on_stack
43 -  debug_object_activate
45 -  debug_object_deactivate
47 -  debug_object_destroy
49 -  debug_object_free
51 -  debug_object_assert_init
53 Each of these functions takes the address of the real object and a
56 Each detected error is reported in the statistics and a limited number
64 Debug functions
67 .. kernel-doc:: lib/debugobjects.c
68    :functions: debug_object_init
79 can deactivate an active object in order to prevent damage to the
90 .. kernel-doc:: lib/debugobjects.c
91    :functions: debug_object_init_on_stack
102 can deactivate an active object in order to prevent damage to the
114 .. kernel-doc:: lib/debugobjects.c
115    :functions: debug_object_activate
126 deactivate an active object in order to prevent damage to the subsystem.
139 .. kernel-doc:: lib/debugobjects.c
140    :functions: debug_object_deactivate
152 .. kernel-doc:: lib/debugobjects.c
153    :functions: debug_object_destroy
156 prevent the usage of invalid objects, which are still available in
166 deactivate an active object in order to prevent damage to the subsystem.
171 .. kernel-doc:: lib/debugobjects.c
172    :functions: debug_object_free
181 object happens. E.g. it can deactivate an active object in order to
188 .. kernel-doc:: lib/debugobjects.c
189    :functions: debug_object_assert_init
197 and other specific initializing functions.
201 Fixup functions
205 ---------------------------------------
207 .. kernel-doc:: include/linux/debugobjects.h
211 -----------
213 This function is called from the debug code whenever a problem in
215 object and the state which is currently recorded in the tracker.
219 -  ODEBUG_STATE_ACTIVE
225 again, after the damage has been repaired in order to keep the state
229 ---------------
231 This function is called from the debug code whenever a problem in
236 -  ODEBUG_STATE_NOTAVAILABLE
238 -  ODEBUG_STATE_ACTIVE
244 function again after the damage has been repaired in order to keep the
251 this is a legitimate case of a statically initialized object or not. In
253 to make the object known to the tracker and marked active. In this case
257 --------------
259 This function is called from the debug code whenever a problem in
264 -  ODEBUG_STATE_ACTIVE
270 -----------
272 This function is called from the debug code whenever a problem in
274 checks in kfree/vfree, when an active object is detected from the
280 -  ODEBUG_STATE_ACTIVE
286 -------------------
288 This function is called from the debug code whenever a problem in
292 ODEBUG_STATE_NOTAVAILABLE when the object is not found in the debug
303 initialized object or not. In this case only debug_object_init()