diff options
| author | Guilherme G. Piccoli <gpiccoli@igalia.com> | 2022-09-29 18:55:15 -0300 |
|---|---|---|
| committer | Kees Cook <keescook@chromium.org> | 2022-09-30 08:16:06 -0700 |
| commit | 40158dbf7eb2b13d8851fe0b875b4c3170ea15db (patch) | |
| tree | d9b0e163ac2fa7179650c5538ec7c1962040518e /fs/fat | |
| parent | 568035b01cfb107af8d2e4bd2fb9aea22cf5b868 (diff) | |
| download | linux-40158dbf7eb2b13d8851fe0b875b4c3170ea15db.tar.gz linux-40158dbf7eb2b13d8851fe0b875b4c3170ea15db.tar.bz2 linux-40158dbf7eb2b13d8851fe0b875b4c3170ea15db.zip | |
Revert "pstore: migrate to crypto acomp interface"
This reverts commit e4f0a7ec586b7644107839f5394fb685cf1aadcc.
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: e4f0a7ec586b ("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
Diffstat (limited to 'fs/fat')
0 files changed, 0 insertions, 0 deletions