Sai Prakash Ranjan 6a4c9ab13f pstore/ram: Fix console ramoops to show the previous boot logs ... commit b05c950698 ("pstore/ram: Simplify ramoops_get_next_prz() arguments") changed update assignment in getting next persistent ram zone by adding a check for record type. But the check always returns true since the record type is assigned 0. And this breaks console ramoops by showing current console log instead of previous log on warm reset and hard reset (actually hard reset should not be showing any logs). Fix this by having persistent ram zone type check instead of record type check. Tested this on SDM845 MTP and dragonboard 410c. Reproducing this issue is simple as below: 1. Trigger hard reset and mount pstore. Will see console-ramoops record in the mounted location which is the current log. 2. Trigger warm reset and mount pstore. Will see the current console-ramoops record instead of previous record. Fixes: b05c950698 ("pstore/ram: Simplify ramoops_get_next_prz() arguments") Signed-off-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org> Acked-by: Joel Fernandes (Google) <joel@joelfernandes.org> [kees: dropped local variable usage] Signed-off-by: Kees Cook <keescook@chromium.org>		2019-01-17 09:14:06 -08:00
..
Kconfig	mm: remove CONFIG_HAVE_MEMBLOCK	2018-10-31 08:54:15 -07:00
Makefile	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
ftrace.c	pstore: Fix bool initialization/comparison	2018-12-03 16:52:35 -08:00
inode.c	pstore: Map PSTORE_TYPE_* to strings	2018-12-03 16:52:35 -08:00
internal.h	pstore: Centralize init/exit routines	2018-10-22 07:11:58 -07:00
platform.c	pstore: Convert buf_lock to semaphore	2018-12-03 17:11:02 -08:00
pmsg.c	Remove 'type' argument from access_ok() function	2019-01-03 18:57:57 -08:00
ram.c	pstore/ram: Fix console ramoops to show the previous boot logs	2019-01-17 09:14:06 -08:00
ram_core.c	Remove 'type' argument from access_ok() function	2019-01-03 18:57:57 -08:00