diff options
| author | Josh Poimboeuf <jpoimboe@kernel.org> | 2022-08-18 09:26:57 -0700 |
|---|---|---|
| committer | Peter Zijlstra <peterz@infradead.org> | 2022-08-19 19:47:57 +0200 |
| commit | 3c6f3900808c483b0bbb2c351f995c7b880dae14 (patch) | |
| tree | e3a0461a9b5c046e5f2b6a9fff315d9c4284203f /tools/objtool | |
| parent | 7b3e31869081771c63c3d006347ad06738f843b5 (diff) | |
objtool: Remove "ANNOTATE_NOENDBR on ENDBR" warning
This warning isn't very useful: why would you put ANNOTATE_NOENDBR on
ENDBR, and if you did, what's the harm?
And thus far it's only found one non-bug, where the
'__end_entry_SYSENTER_compat' label happens to land on the ENDBR from
entry_SYSCALL_compat:
vmlinux.o: warning: objtool: entry_SYSCALL_compat+0x0: ANNOTATE_NOENDBR on ENDBR
.. which is fine. Just remove the warning.
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/142341a5dafdfc788e4c95b9e226a6eefc9b626e.1660839773.git.jpoimboe@kernel.org
Diffstat (limited to 'tools/objtool')
| -rw-r--r-- | tools/objtool/check.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/tools/objtool/check.c b/tools/objtool/check.c index b012d987a658..8b8c8f74a775 100644 --- a/tools/objtool/check.c +++ b/tools/objtool/check.c @@ -2102,9 +2102,6 @@ static int read_noendbr_hints(struct objtool_file *file) return -1; } - if (insn->type == INSN_ENDBR) - WARN_FUNC("ANNOTATE_NOENDBR on ENDBR", insn->sec, insn->offset); - insn->noendbr = 1; } |