Joel Fernandes (Google) fffdbf5868 pstore/ram: Do not treat empty buffers as valid ... [ Upstream commit 30696378f6 ] The ramoops backend currently calls persistent_ram_save_old() even if a buffer is empty. While this appears to work, it is does not seem like the right thing to do and could lead to future bugs so lets avoid that. It also prevents misleading prints in the logs which claim the buffer is valid. I got something like: found existing buffer, size 0, start 0 When I was expecting: no valid data in buffer (sig = ...) This bails out early (and reports with pr_debug()), since it's an acceptable state. Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org> Co-developed-by: Kees Cook <keescook@chromium.org> Signed-off-by: Kees Cook <keescook@chromium.org> Signed-off-by: Sasha Levin <sashal@kernel.org>		2019-01-26 09:38:33 +01: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
ftrace.c	pstore: add pstore unregister	2015-10-22 08:59:18 -07:00
inode.c	fs: Replace CURRENT_TIME with current_time() for inode timestamps	2016-09-27 21:06:21 -04:00
internal.h	pstore: Fix return type of pstore_is_mounted()	2015-10-22 10:57:33 -07:00
platform.c	pstore: Convert console write to use ->write_buf	2018-12-17 09:38:35 +01:00
pmsg.c	pstore/pmsg: drop bounce buffer	2016-09-08 15:01:10 -07:00
ram.c	pstore: Allow prz to control need for locking	2017-08-06 18:59:43 -07:00
ram_core.c	pstore/ram: Do not treat empty buffers as valid	2019-01-26 09:38:33 +01:00