Namhyung Kim 70ad35db33 pstore: Convert console write to use ->write_buf ... Maybe I'm missing something, but I don't know why it needs to copy the input buffer to psinfo->buf and then write. Instead we can write the input buffer directly. The only implementation that supports console message (i.e. ramoops) already does it for ftrace messages. For the upcoming virtio backend driver, it needs to protect psinfo->buf overwritten from console messages. If it could use ->write_buf method instead of ->write, the problem will be solved easily. Cc: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Namhyung Kim <namhyung@kernel.org> Signed-off-by: Kees Cook <keescook@chromium.org>		2016-11-15 16:34:32 -08:00
..
ftrace.c	pstore: Use global ftrace filters for function trace filtering	2016-11-15 16:34:30 -08:00
inode.c	pstore: Protect unlink with read_mutex	2016-11-15 16:34:31 -08:00
internal.h	pstore: Add ftrace timestamp counter	2016-11-15 16:34:27 -08:00
Kconfig	pstore: add lzo/lz4 compression support	2016-06-02 10:59:31 -07:00
Makefile	pstore: add pstore unregister	2015-10-22 08:59:18 -07:00
platform.c	pstore: Convert console write to use ->write_buf	2016-11-15 16:34:32 -08:00
pmsg.c	pstore/pmsg: drop bounce buffer	2016-09-08 15:01:10 -07:00
ram_core.c	pstore: Allow prz to control need for locking	2016-11-15 16:34:25 -08:00
ram.c	pstore: Clarify context field przs as dprzs	2016-11-15 16:34:29 -08:00