x86/dumpstack: Explain the reasoning for the prologue and buffer size
authorBorislav Petkov <bp@suse.de>
Tue, 17 Apr 2018 16:11:24 +0000 (18:11 +0200)
committerThomas Gleixner <tglx@linutronix.de>
Thu, 26 Apr 2018 14:15:28 +0000 (16:15 +0200)
commit4dba072cd097f35fa8f77c49d909ada2b079a4c4
treef06c2b012989f44e0c5776e1e26c360e1527c354
parent602bd705da334f214fc03db328dc37d2f1f33307
x86/dumpstack: Explain the reasoning for the prologue and buffer size

The whole reasoning behind the amount of opcode bytes dumped and prologue
length isn't very clear so write down some of the reasons for why it is
done the way it is.

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-10-bp@alien8.de
arch/x86/kernel/dumpstack.c