Lines Matching refs:of
13 such variables, depending on the chosen level of coverage.
31 This option enables initialization of stack variables at
35 on the function calling complexity of a given workload's
38 This chooses the level of coverage over classes of potentially
47 classes of uninitialized stack variable exploits
56 a __user attribute. This can prevent some classes of
70 of uninitialized stack variable exploits and information
74 As a side-effect, this keeps a lot of variables on the
88 of uninitialized stack variable exploits and information
97 of uninitialized stack variable exploits and information
119 returning from system calls. This has the effect of leaving
121 the lifetime of any sensitive stack contents and reduces
126 impact being driven by the depth of the stack usage, rather than
139 int "Minimum stack frame size of functions tracked by STACKLEAK"
145 the lowest border of the kernel stack (and for some other purposes).
163 bool "Allow runtime disabling of kernel stack erasing"
173 This has the effect of setting "init_on_alloc=1" on the kernel
177 many kinds of "uninitialized heap memory" flaws, especially
185 This has the effect of setting "init_on_free=1" on the kernel
189 when freed, eliminating many kinds of "uninitialized heap memory"
195 than "init_on_alloc" due to the negative cache effects of