diff options
author | Petr Mladek <[email protected]> | 2016-12-14 15:05:52 -0800 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2016-12-14 16:04:08 -0800 |
commit | d1bd8ead126668a2d6c42d97cc3664e95b3fa1dc (patch) | |
tree | 39c0cf2d482c762c17a4fe9ce90f72b6ea9424ce /tools/perf/scripts/python/net_dropmonitor.py | |
parent | 2d13bb6494c807bcf3f78af0e96c0b8615a94385 (diff) |
kdb: remove unused kdb_event handling
kdb_event state variable is only set but never checked in the kernel
code.
http://www.spinics.net/lists/kdb/msg01733.html suggests that this
variable affected WARN_CONSOLE_UNLOCKED() in the original
implementation. But this check never went upstream.
The semantic is unclear and racy. The value is updated after the
kdb_printf_lock is acquired and after it is released. It should be
symmetric at minimum. The value should be manipulated either inside or
outside the locked area.
Fortunately, it seems that the original function is gone and we could
simply remove the state variable.
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Petr Mladek <[email protected]>
Suggested-by: Daniel Thompson <[email protected]>
Cc: Jason Wessel <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Sergey Senozhatsky <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions