Lines Matching refs:objtool

4 The kernel CONFIG_OBJTOOL option enables a host tool named 'objtool'
59 objtool cmdline.
65 Typically, objtool runs on every translation unit (TU, aka ".o file") in
80              TU: objtool [--module] <options>
85              TU: objtool [--module] <options>	// no --noinstr
86         vmlinux: objtool --noinstr		// other options removed
91         vmlinux: objtool --noinstr <options>
92          module: objtool --module --noinstr <options>
168    The benefit of objtool here is that because it ensures that *all*
196 To achieve the validation, objtool enforces the following rules:
200    ENTRY/ENDPROC macros.  If objtool finds a return instruction
204    This rule is needed so that objtool can properly identify each
211    This rule is needed so that objtool can ignore non-callable code.
231    This rule is needed so that objtool can reliably analyze all of a
233    and it's not a sibling call, objtool has no way to follow the jump
256 Here are some examples of common warnings reported by objtool, what
258 the objtool maintainers.
261 1. file.o: warning: objtool: func()+0x128: call without frame pointer save/setup
283 2. file.o: warning: objtool: .text+0x53: unreachable instruction
291    macros in asm/unwind_hints.h so objtool and the unwinder can know the
295    a just a bad person, you can tell objtool to ignore it.  See the
302 4. file.o: warning: objtool: func(): can't find starting instruction
304    file.o: warning: objtool: func()+0x11dd: can't decode instruction
307    objtool's instruction decoder.  Move the data to a more appropriate
311 5. file.o: warning: objtool: func()+0x6: unsupported instruction in callable function
320 6. file.o: warning: objtool: func()+0x26: sibling call from callable instruction with modified stac…
334 7. file: warning: objtool: func()+0x5c: stack state mismatch
351 8. file.o: warning: objtool: funcA() falls through to next function funcB()
354    unconditional jump, and that objtool has determined that the function
360       objtool's hard-coded global_noreturns array.  Feel free to bug the
361       objtool maintainer, or you can submit a patch.
370 9. file.o: warning: objtool: funcA() call to funcB() with UACCESS enabled
391    3) add funcB to uaccess_safe_builtin whitelist in tools/objtool/check.c, if
414 If the error doesn't seem to make sense, it could be a bug in objtool.
415 Feel free to ask the objtool maintainer for help.
421 If you _really_ need objtool to ignore something, and are 100% sure
422 that it won't affect kernel stack traces, you can tell objtool to