-----Original Message-----If the decompression fails and openssl doesn't work, the worst case is that users can't read the entry.
From: linux-kernel-owner@xxxxxxxxxxxxxxx [mailto:linux-kernel-owner@xxxxxxxxxxxxxxx] On Behalf Of Aruna Balakrishnaiah
Sent: Friday, August 16, 2013 9:18 AM
To: linuxppc-dev@xxxxxxxxxx; tony.luck@xxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; keescook@xxxxxxxxxxxx
Cc: jkenisto@xxxxxxxxxxxxxxxxxx; ananth@xxxxxxxxxx; benh@xxxxxxxxxxxxxxxxxxx; cbouatmailru@xxxxxxxxx;
mahesh@xxxxxxxxxxxxxxxxxx; ccross@xxxxxxxxxxx
Subject: [RFC PATCH v2 06/11] pstore: Add decompression support to pstore
Based on the flag 'compressed' set or not, pstore will decompress the
data returning a plain text file. If decompression fails for a particular
record it will have the compressed data in the file which can be
decompressed with 'openssl' command line tool.
In that case, pstore is meaningless at all.
Also, for users who want to get a single panic message, a compression is not needed.
So, I think we still have to support non-compression mode.
(IMO, pstore can take kdump as a model. Kdump supports both compression and non-compression mode.)
But, if you think my comment is outside this patchset, it's OK.
We can make it with a separate patch.
Seiji
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@xxxxxxxxxxxxxxxx
https://lists.ozlabs.org/listinfo/linuxppc-dev