diff options
author | Linus Torvalds | 2020-06-27 08:53:49 -0700 |
---|---|---|
committer | Linus Torvalds | 2020-06-27 08:53:49 -0700 |
commit | 6116dea80dfd5b8d3825bf7f2e44a8bc2730f3d0 (patch) | |
tree | 729a8797b2a27ab9a1b6d38cb4a67b789e2238fa /net/hsr | |
parent | 21d2f6850c09fdec730c11d35406da1dc541432d (diff) | |
parent | 440ab9e10e2e6e5fd677473ee6f9e3af0f6904d6 (diff) |
Merge tag 'kgdb-5.8-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux
Pull kgdb fixes from Daniel Thompson:
"The main change here is a fix for a number of unsafe interactions
between kdb and the console system. The fixes are specific to kdb
(pure kgdb debugging does not use the console system at all). On
systems with an NMI then kdb, if it is enabled, must get messages to
the user despite potentially running from some "difficult" calling
contexts. These fixes avoid using the console system where we have
been provided an alternative (safer) way to interact with the user
and, if using the console system in unavoidable, use oops_in_progress
for deadlock avoidance. These fixes also ensure kdb honours the
console enable flag.
Also included is a fix that wraps kgdb trap handling in an RCU read
lock to avoids triggering diagnostic warnings. This is a wide lock
scope but this is OK because kgdb is a stop-the-world debugger. When
we stop the world we put all the CPUs into holding pens and this
inhibits RCU update anyway"
* tag 'kgdb-5.8-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux:
kgdb: Avoid suspicious RCU usage warning
kdb: Switch to use safer dbg_io_ops over console APIs
kdb: Make kdb_printf() console handling more robust
kdb: Check status of console prior to invoking handlers
kdb: Re-factor kdb_printf() message write code
Diffstat (limited to 'net/hsr')
0 files changed, 0 insertions, 0 deletions