diff options
| author | John Ogness <john.ogness@linutronix.de> | 2022-11-16 19:21:19 +0300 |
|---|---|---|
| committer | Petr Mladek <pmladek@suse.com> | 2022-12-02 13:24:59 +0300 |
| commit | 3860e7c57fd23e744e045436f9872fb9d01381e2 (patch) | |
| tree | 1e3b1edbb9eff00d99f8ad6a37d2bbcd3b8a5cdc /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | a42427609368d773c4ab6b4c9686577817a4d219 (diff) | |
| download | linux-3860e7c57fd23e744e045436f9872fb9d01381e2.tar.xz | |
um: kmsg_dump: only dump when no output console available
The initial intention of the UML kmsg_dumper is to dump the kernel
buffers to stdout if there is no console available to perform the
regular crash output.
However, if ttynull was registered as a console, no crash output was
seen. Commit e23fe90dec28 ("um: kmsg_dumper: always dump when not tty
console") tried to fix this by performing the kmsg_dump unless the
stdio console was behind /dev/console or enabled. But this allowed
kmsg dumping to occur even if other non-stdio consoles will output
the crash output. Also, a console being the driver behind
/dev/console has nothing to do with a crash scenario.
Restore the initial intention by dumping the kernel buffers to stdout
only if a non-ttynull console is registered and enabled. Also add
detailed comments so that it is clear why these rules are applied.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Signed-off-by: Petr Mladek <pmladek@suse.com>
Link: https://lore.kernel.org/r/20221116162152.193147-8-john.ogness@linutronix.de
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions