x86/fault: Dump user opcode bytes on fatal faults
authorBorislav Petkov <bp@suse.de>
Tue, 17 Apr 2018 16:11:21 +0000 (18:11 +0200)
committerThomas Gleixner <tglx@linutronix.de>
Thu, 26 Apr 2018 14:15:27 +0000 (16:15 +0200)
commitba54d856a9d8a9c56b87e20c88602b7e3cb568fb
tree06e0a76f06eadfd0faacb55ccec653b210d5afb9
parente8b6f984516b1fcb0ccf4469ca42777c9c2dc76d
x86/fault: Dump user opcode bytes on fatal faults

Sometimes it is useful to see which user opcode bytes RIP points to
when a fault happens: be it to rule out RIP corruption, to dump info
early during boot, when doing core dumps is impossible due to not having
a writable filesystem yet.

Sometimes it is useful if debugging an issue and one doesn't have access
to the executable which caused the fault in order to disassemble it.

That last aspect might have some security implications so
show_unhandled_signals could be revisited for that or a new config option
added.

Signed-off-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Lutomirski <luto@amacapital.net>
Link: https://lkml.kernel.org/r/20180417161124.5294-7-bp@alien8.de
arch/x86/mm/fault.c