Lines Matching refs:stack

19   stack traces are reliable for live patching
98 Objtool's stack validation feature analyzes every .o file and ensures
99 the validity of its stack metadata.  It enforces a set of rules on asm
100 code and C inline assembly code so that stack traces can be reliable.
111 Here are some of the benefits of validating stack metadata:
113 a) More reliable stack traces for frame pointer enabled kernels
116    code and debug tools to be able to walk the stack to determine the
131    For stack traces based on frame pointers to be reliable, all
132    functions which call other functions must first create a stack frame
134    create a stack frame before calling a second function, the *caller*
135    of the first function will be skipped on the stack trace.
165    skipped.  Instead the stack trace seems to show that
170    skipped on a stack trace.
173        beginning of a function before the stack frame has been created,
174        or at the very end of the function after the stack frame has been
180    used to walk the stack.  Unlike frame pointers, ORC data is out of
190    stack traces need to be reliable (or an unreliable condition needs to
205    callable function in order to analyze its stack metadata.
219    This rule ensures that frame pointer based stack traces will work as
220    designed.  If function A doesn't create a stack frame before calling
221    function B, the _caller_ of function A will be skipped on the stack
280    stack pointer in its output operand.  On x86_64, this means adding
285    Otherwise the stack frame may not get created before the call.
316    stack state associated with the code.
318    If you're 100% sure the code won't affect stack traces, or if you're
349 ….o: warning: objtool: func()+0x26: sibling call from callable instruction with modified stack frame
363 7. file: warning: objtool: func()+0x5c: stack state mismatch
375    does some unusual things to the stack or the frame pointer.  In such
425 10. file.o: warning: func()+0x5c: stack layout conflict in alternatives
428     macro, the code paths have conflicting modifications to the stack.
433     NOPs to shift the stack changes around so they no longer conflict.
459 that it won't affect kernel stack traces, you can tell objtool to