Lines Matching refs:stack
19 stack traces are reliable for live patching
110 Objtool's stack validation feature analyzes every .o file and ensures
111 the validity of its stack metadata. It enforces a set of rules on asm
112 code and C inline assembly code so that stack traces can be reliable.
123 Here are some of the benefits of validating stack metadata:
125 a) More reliable stack traces for frame pointer enabled kernels
128 code and debug tools to be able to walk the stack to determine the
143 For stack traces based on frame pointers to be reliable, all
144 functions which call other functions must first create a stack frame
146 create a stack frame before calling a second function, the *caller*
147 of the first function will be skipped on the stack trace.
177 skipped. Instead the stack trace seems to show that
182 skipped on a stack trace.
185 beginning of a function before the stack frame has been created,
186 or at the very end of the function after the stack frame has been
192 used to walk the stack. Unlike frame pointers, ORC data is out of
202 stack traces need to be reliable (or an unreliable condition needs to
217 callable function in order to analyze its stack metadata.
220 otherwise doing funny things with the stack or registers, should
229 This rule ensures that frame pointer based stack traces will work as
230 designed. If function A doesn't create a stack frame before calling
231 function B, the _caller_ of function A will be skipped on the stack
290 stack pointer in its output operand. On x86_64, this means adding
295 Otherwise the stack frame may not get created before the call.
329 If you're sure the code won't affect the reliability of runtime stack
358 ….o: warning: objtool: func()+0x26: sibling call from callable instruction with modified stack frame
361 sibling call and detected that the stack wasn't first restored to its
371 7. file: warning: objtool: func()+0x5c: stack state mismatch
383 does some unusual things to the stack or the frame pointer. In such
432 10. file.o: warning: func()+0x5c: stack layout conflict in alternatives
435 macro, the code paths have conflicting modifications to the stack.
440 NOPs to shift the stack changes around so they no longer conflict.
468 that it won't affect kernel stack traces, you can tell objtool to