Lines Matching +full:keep +full:- +full:a +full:- +full:live

2 The object-lifetime debugging infrastructure
10 debugobjects is a generic infrastructure to track the life time of
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
23 with a kernel command line option.
28 A kernel subsystem needs to provide a data structure which describes the
33 information can be retrieved from a live system instead of hard core
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
57 of errors are printk'ed including a full stack trace.
67 .. kernel-doc:: lib/debugobjects.c
70 This function is called whenever the initialization function of a real
83 allocates a tracker object for the real object and sets the tracker
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
90 .. kernel-doc:: lib/debugobjects.c
93 This function is called whenever the initialization function of a real
106 allocates a tracker object for the real object and sets the tracker
112 object returns. Otherwise we keep track of stale objects.
114 .. kernel-doc:: lib/debugobjects.c
117 This function is called whenever the activation function of a real
139 .. kernel-doc:: lib/debugobjects.c
142 This function is called whenever the deactivation function of a real
152 .. kernel-doc:: lib/debugobjects.c
171 .. kernel-doc:: lib/debugobjects.c
188 .. kernel-doc:: lib/debugobjects.c
205 ---------------------------------------
207 .. kernel-doc:: include/linux/debugobjects.h
211 -----------
213 This function is called from the debug code whenever a problem in
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
247 The activation of statically initialized objects is a special case. When
251 this is a legitimate case of a statically initialized object or not. In
254 the function should return false because this is not a real fixup.
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
280 -  ODEBUG_STATE_ACTIVE
286 -------------------
288 This function is called from the debug code whenever a problem in
291 Called from debug_object_assert_init() with a hardcoded state
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.