Re: pstore: fix compression

2021-02-18 Thread Jiri Bohac
On Thu, Feb 18, 2021 at 12:30:03PM -0800, Kees Cook wrote: > Eek; thanks for the catch! thanks for applying the fix; BTW, with the compression broken, I was not getting any dmesg stored in ERST at all, not even uncompressed. After instrumenting the code with a lot of debug printks I found that wr

Re: pstore: fix compression

2021-02-18 Thread Kees Cook
On Thu, 18 Feb 2021 12:15:47 +0100, Jiri Bohac wrote: > pstore_compress() and decompress_record() use a mistyped config option > name ("PSTORE_COMPRESSION" instead of "PSTORE_COMPRESS"). > As a result compression and decompressionm of pstore records is always > disabled. > > Use the correct config

Re: pstore: fix compression

2021-02-18 Thread Greg KH
On Thu, Feb 18, 2021 at 12:15:47PM +0100, Jiri Bohac wrote: > pstore_compress() and decompress_record() use a mistyped config option > name ("PSTORE_COMPRESSION" instead of "PSTORE_COMPRESS"). > As a result compression and decompressionm of pstore records is always > disabled. > > Use the correct

Re: pstore: fix compression

2021-02-18 Thread Matteo Croce
On Thu, Feb 18, 2021 at 12:15 PM Jiri Bohac wrote: > > pstore_compress() and decompress_record() use a mistyped config option > name ("PSTORE_COMPRESSION" instead of "PSTORE_COMPRESS"). > As a result compression and decompressionm of pstore records is always > disabled. > > Use the correct config

pstore: fix compression

2021-02-18 Thread Jiri Bohac
pstore_compress() and decompress_record() use a mistyped config option name ("PSTORE_COMPRESSION" instead of "PSTORE_COMPRESS"). As a result compression and decompressionm of pstore records is always disabled. Use the correct config option name. Signed-off-by: Jiri Bohac Fixes: fd49e03280e596e54