summaryrefslogtreecommitdiff
path: root/mm/highmem.c
diff options
context:
space:
mode:
authorBorislav Petkov <bp@suse.de>2018-04-17 19:11:21 +0300
committerThomas Gleixner <tglx@linutronix.de>2018-04-26 17:15:27 +0300
commitba54d856a9d8a9c56b87e20c88602b7e3cb568fb (patch)
tree06e0a76f06eadfd0faacb55ccec653b210d5afb9 /mm/highmem.c
parente8b6f984516b1fcb0ccf4469ca42777c9c2dc76d (diff)
downloadlinux-ba54d856a9d8a9c56b87e20c88602b7e3cb568fb.tar.xz
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
Diffstat (limited to 'mm/highmem.c')
0 files changed, 0 insertions, 0 deletions