Joel Fernandes (Google) e1e3a46706 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:37:02 +01:00
..
ftrace.c	pstore: Remove write_buf() callback	2017-03-07 14:01:02 -08:00
inode.c	Revert "pstore: Honor dmesg_restrict sysctl on dmesg dumps"	2017-08-17 16:29:19 -07:00
internal.h	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
Kconfig	docs: fix locations of several documents that got moved	2016-10-24 08:12:35 -02:00
Makefile	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
platform.c	Merge branch 'work.mount' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs	2017-07-15 12:00:42 -07:00
pmsg.c	pstore: Create common record initializer	2017-05-31 10:13:44 -07:00
ram_core.c	pstore/ram: Do not treat empty buffers as valid	2019-01-26 09:37:02 +01:00
ram.c	pstore/ram: Avoid allocation and leak of platform data	2019-01-23 08:09:49 +01:00