pstore: Move kmsg_bytes default into Kconfig
authorVasile-Laurentiu Stanimir <vasile-laurentiu.stanimir@windriver.com>
Wed, 4 Nov 2020 13:05:32 +0000 (15:05 +0200)
committerKees Cook <keescook@chromium.org>
Tue, 1 Dec 2020 20:09:17 +0000 (12:09 -0800)
commit26fecbf7602dd69b649914e61526bd67c557fece
tree1f412679073b9efebb805e81a078b32b00328c9c
parentb6f8ed33ab2bbc58e40fb1e2fb0f9c90cab04baf
pstore: Move kmsg_bytes default into Kconfig

While kmsg_bytes can be set for pstore via mount, if a crash occurs
before the mount only partial console log will be stored as kmsg_bytes
defaults to a potentially different hardcoded value in the kernel
(PSTORE_DEFAULT_KMSG_BYTES). This makes it impossible to analyze valuable
post-mortem data especially on the embedded development or in the process
of bringing up new boards. Change this value to be a Kconfig option
with the default of old PSTORE_DEFAULT_KMSG_BYTES

Signed-off-by: Vasile-Laurentiu Stanimir <vasile-laurentiu.stanimir@windriver.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
fs/pstore/Kconfig
fs/pstore/inode.c
fs/pstore/internal.h
fs/pstore/platform.c