diff options
| author |   Daniel Thompson <daniel.thompson@linaro.org> | 2014-11-06 15:32:13 +0000 |
|---|---|---|
| committer |   Jason Wessel <jason.wessel@windriver.com> | 2015-02-19 12:39:02 -0600 |
| commit | 5454388113938d9592d6a6d5424469014da4ee86 (patch) | |
| tree | 0765c2a49d358edb97bd170f29dc90904e990b5b /kernel/tsacct.c | |
| parent | kdb: Avoid printing KERN_ levels to consoles (diff) | |
| download | linux-dev-5454388113938d9592d6a6d5424469014da4ee86.tar.xz linux-dev-5454388113938d9592d6a6d5424469014da4ee86.zip | |
kdb: Remove stack dump when entering kgdb due to NMI
Issuing a stack dump feels ergonomically wrong when entering due to NMI.
Entering due to NMI is normally a reaction to a user request, either the
NMI button on a server or a "magic knock" on a UART. Therefore the
backtrace behaviour on entry due to NMI should be like SysRq-g (no stack
dump) rather than like oops.
Note also that the stack dump does not offer any information that
cannot be trivial retrieved using the 'bt' command.
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Diffstat (limited to 'kernel/tsacct.c')
0 files changed, 0 insertions, 0 deletions