Lines Matching full:stack

1 Compile-time stack metadata validation
10 analyzes every .o file and ensures the validity of its stack metadata.
12 that stack traces can be reliable.
28 Why do we need stack metadata validation?
31 Here are some of the benefits of validating stack metadata:
33 a) More reliable stack traces for frame pointer enabled kernels
36    code and debug tools to be able to walk the stack to determine the
51    For stack traces based on frame pointers to be reliable, all
52    functions which call other functions must first create a stack frame
54    create a stack frame before calling a second function, the *caller*
55    of the first function will be skipped on the stack trace.
85    skipped.  Instead the stack trace seems to show that
90    skipped on a stack trace.
93        beginning of a function before the stack frame has been created,
94        or at the very end of the function after the stack frame has been
100    used to walk the stack.  Unlike frame pointers, ORC data is out of
110    stack traces need to be reliable (or an unreliable condition needs to
128    callable function in order to analyze its stack metadata.
142    This rule ensures that frame pointer based stack traces will work as
143    designed.  If function A doesn't create a stack frame before calling
144    function B, the _caller_ of function A will be skipped on the stack
197    stack pointer in its output operand.  On x86_64, this means adding
202    Otherwise the stack frame may not get created before the call.
214    stack state associated with the code.
216    If you're 100% sure the code won't affect stack traces, or if you're
242 ….o: warning: objtool: func()+0x26: sibling call from callable instruction with modified stack frame
256 7. file: warning: objtool: func()+0x5c: stack state mismatch
268    does some unusual things to the stack or the frame pointer.  In such
318 10. file.o: warning: func()+0x5c: stack layout conflict in alternatives
321     macro, the code paths have conflicting modifications to the stack.
326     NOPs to shift the stack changes around so they no longer conflict.
344 that it won't affect kernel stack traces, you can tell objtool to