summaryrefslogtreecommitdiff
path: root/Documentation/networking/tproxy.txt
diff options
context:
space:
mode:
authorJose Abreu <Jose.Abreu@synopsys.com>2017-09-01 19:00:23 +0300
committerVineet Gupta <vgupta@synopsys.com>2017-09-01 21:29:05 +0300
commit1ee55a8f7f6b7ca4c0c59e0b4b4e3584a085c2d3 (patch)
treeb04b36aa2678527e951a7e3d7262926149ac2228 /Documentation/networking/tproxy.txt
parentaa7e3a5e8b63628c7fc131effc163ade08ced41b (diff)
downloadlinux-1ee55a8f7f6b7ca4c0c59e0b4b4e3584a085c2d3.tar.xz
ARC: Re-enable MMU upon Machine Check exception
I recently came upon a scenario where I would get a double fault machine check exception tiriggered by a kernel module. However the ensuing crash stacktrace (ksym lookup) was not working correctly. Turns out that machine check auto-disables MMU while modules are allocated in kernel vaddr spapce. This patch re-enables the MMU before start printing the stacktrace making stacktracing of modules work upon a fatal exception. Cc: stable@kernel.org Signed-off-by: Jose Abreu <joabreu@synopsys.com> Reviewed-by: Alexey Brodkin <abrodkin@synopsys.com> Signed-off-by: Vineet Gupta <vgupta@synopsys.com> [vgupta: moved code into low level handler to avoid in 2 places]
Diffstat (limited to 'Documentation/networking/tproxy.txt')
0 files changed, 0 insertions, 0 deletions