x86/unwind/orc: Silence warnings caused by missing ORC data
authorJosh Poimboeuf <jpoimboe@redhat.com>
Fri, 5 Feb 2021 14:24:03 +0000 (08:24 -0600)
committerBorislav Petkov <bp@suse.de>
Sat, 6 Mar 2021 12:09:45 +0000 (13:09 +0100)
commitb59cc97674c947861783ca92b9a6e7d043adba96
treea742f77c4b80d7cd555b4f96c8736ea3b92f6999
parente504e74cc3a2c092b05577ce3e8e013fae7d94e6
x86/unwind/orc: Silence warnings caused by missing ORC data

The ORC unwinder attempts to fall back to frame pointers when ORC data
is missing for a given instruction.  It sets state->error, but then
tries to keep going as a best-effort type of thing.  That may result in
further warnings if the unwinder gets lost.

Until we have some way to register generated code with the unwinder,
missing ORC will be expected, and occasionally going off the rails will
also be expected.  So don't warn about it.

Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Borislav Petkov <bp@suse.de>
Tested-by: Ivan Babrou <ivan@cloudflare.com>
Link: https://lkml.kernel.org/r/06d02c4bbb220bd31668db579278b0352538efbb.1612534649.git.jpoimboe@redhat.com
arch/x86/kernel/unwind_orc.c