Guilherme G. Piccoli 40158dbf7e Revert "pstore: migrate to crypto acomp interface" ... This reverts commit e4f0a7ec58. When using this new interface, both efi_pstore and ramoops backends are unable to properly decompress dmesg if using zstd, lz4 and lzo algorithms (and maybe more). It does succeed with deflate though. The message observed in the kernel log is: [2.328828] pstore: crypto_acomp_decompress failed, ret = -22! The pstore infrastructure is able to collect the dmesg with both backends tested, but since decompression fails it's unreadable. With this revert everything is back to normal. Fixes: e4f0a7ec58 ("pstore: migrate to crypto acomp interface") Cc: Ard Biesheuvel <ardb@kernel.org> Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com> Signed-off-by: Kees Cook <keescook@chromium.org> Link: https://lore.kernel.org/r/20220929215515.276486-1-gpiccoli@igalia.com		2022-09-30 08:16:06 -07:00
..
blk.c	pstore/blk: Use "%lu" to format unsigned long	2021-11-21 09:44:19 -08:00
ftrace.c	pstore/ftrace: Allow immediate recording	2021-11-18 10:29:52 -08:00
inode.c	pstore: Add priv field to pstore_record for backend specific use	2022-06-24 20:40:04 +02:00
internal.h	pstore: Move kmsg_bytes default into Kconfig	2020-12-01 12:09:17 -08:00
Kconfig	Revert "mark pstore-blk as broken"	2021-11-16 17:23:42 -07:00
Makefile
platform.c	Revert "pstore: migrate to crypto acomp interface"	2022-09-30 08:16:06 -07:00
pmsg.c
ram_core.c	pstore: Add prefix to ECC messages	2022-03-01 10:36:59 -08:00
ram.c	pstore: Add mem_type property DT parsing support	2021-03-31 10:06:23 -07:00
zone.c	pstore/zone: cleanup "rcnt" type	2022-06-23 08:27:52 -07:00