diff options
author | Sumit Garg <sumit.garg@linaro.org> | 2021-01-22 14:05:56 +0300 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-03-04 11:39:31 +0300 |
commit | 2040647cbff14f19a8fe52022fdc73a5bdc73c91 (patch) | |
tree | b8104ccc360abe97a88f8b07837eb53a433aec76 /drivers/pci | |
parent | 8a5e6d954a3c527ea66d3c36a73469d6af5aec6c (diff) | |
download | linux-2040647cbff14f19a8fe52022fdc73a5bdc73c91.tar.xz |
kdb: Make memory allocations more robust
commit 93f7a6d818deef69d0ba652d46bae6fbabbf365c upstream.
Currently kdb uses in_interrupt() to determine whether its library
code has been called from the kgdb trap handler or from a saner calling
context such as driver init. This approach is broken because
in_interrupt() alone isn't able to determine kgdb trap handler entry from
normal task context. This can happen during normal use of basic features
such as breakpoints and can also be trivially reproduced using:
echo g > /proc/sysrq-trigger
We can improve this by adding check for in_dbg_master() instead which
explicitly determines if we are running in debugger context.
Cc: stable@vger.kernel.org
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
Link: https://lore.kernel.org/r/1611313556-4004-1-git-send-email-sumit.garg@linaro.org
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/pci')
0 files changed, 0 insertions, 0 deletions