]> git.baikalelectronics.ru Git - kernel.git/commit
pstore/ram: Introduce max_reason and convert dump_oops
authorKees Cook <keescook@chromium.org>
Wed, 13 May 2020 21:35:03 +0000 (14:35 -0700)
committerKees Cook <keescook@chromium.org>
Sat, 30 May 2020 17:34:03 +0000 (10:34 -0700)
commit1747f652daf703d25dafb596e9f2518bc82e9fea
tree840bdcf480412bd162005b70d4609e31c33087da
parentf441e68ebed8f1a06065b830ec69adb8d90cb945
pstore/ram: Introduce max_reason and convert dump_oops

Now that pstore_register() can correctly pass max_reason to the kmesg
dump facility, introduce a new "max_reason" module parameter and
"max-reason" Device Tree field.

The "dump_oops" module parameter and "dump-oops" Device
Tree field are now considered deprecated, but are now automatically
converted to their corresponding max_reason values when present, though
the new max_reason setting has precedence.

For struct ramoops_platform_data, the "dump_oops" member is entirely
replaced by a new "max_reason" member, with the only existing user
updated in place.

Additionally remove the "reason" filter logic from ramoops_pstore_write(),
as that is not specifically needed anymore, though technically
this is a change in behavior for any ramoops users also setting the
printk.always_kmsg_dump boot param, which will cause ramoops to behave as
if max_reason was set to KMSG_DUMP_MAX.

Co-developed-by: Pavel Tatashin <pasha.tatashin@soleen.com>
Signed-off-by: Pavel Tatashin <pasha.tatashin@soleen.com>
Link: https://lore.kernel.org/lkml/20200515184434.8470-6-keescook@chromium.org/
Signed-off-by: Kees Cook <keescook@chromium.org>
Documentation/admin-guide/ramoops.rst
drivers/platform/chrome/chromeos_pstore.c
fs/pstore/ram.c
include/linux/pstore_ram.h