diff options
author | Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> | 2018-04-19 03:42:50 +0200 |
---|---|---|
committer | Petr Mladek <pmladek@suse.com> | 2018-04-25 13:26:02 +0200 |
commit | 43a17111c2553925f65e7be9b9c3f9d90cf29a8b (patch) | |
tree | 3e14a2ad36779608bc6d4d3bfbdb12ef6c5482d2 /kernel/printk/printk_safe.c | |
parent | Merge branch 'for-4.17' of git://git.kernel.org/pub/scm/linux/kernel/git/pmla... (diff) | |
download | linux-43a17111c2553925f65e7be9b9c3f9d90cf29a8b.tar.xz linux-43a17111c2553925f65e7be9b9c3f9d90cf29a8b.zip |
printk: wake up klogd in vprintk_emit
We wake up klogd very late - only when current console_sem owner
is done pushing pending kernel messages to the serial/net consoles.
In some cases this results in lost syslog messages, because kernel
log buffer is a circular buffer and if we don't wakeup syslog long
enough there are chances that logbuf simply will wrap around.
The patch moves the klogd wake up call to vprintk_emit(), which is
the only legit way for a kernel message to appear in the logbuf,
right after the attempt to handle consoles. As a result, klogd
will get waken either after flushing the new message to consoles
or immediately when consoles are still busy with older messages.
Link: http://lkml.kernel.org/r/20180419014250.5692-1-sergey.senozhatsky@gmail.com
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Signed-off-by: Petr Mladek <pmladek@suse.com>
Diffstat (limited to 'kernel/printk/printk_safe.c')
0 files changed, 0 insertions, 0 deletions