On Friday 23 August 2013 04:34 AM, Seiji Aguchi wrote:
-----Original Message-----
From: linux-kernel-ow...@vger.kernel.org
[mailto:linux-kernel-ow...@vger.kernel.org] On Behalf Of Aruna Balakrishnaiah
Sent: Friday, August 16, 2013 9:18 AM
To: linuxppc-...@ozlabs.org; tony.l...@intel.com; linux-kernel@vger.kernel.org;
keesc...@chromium.org
Cc: jkeni...@linux.vnet.ibm.com; ana...@in.ibm.com; b...@kernel.crashing.org;
cbouatmai...@gmail.com;
mah...@linux.vnet.ibm.com; ccr...@android.com
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.
If the decompression fails and openssl doesn't work, the worst case is that
users can't read the entry.
In that case, pstore is meaningless at all.
If decompression fails and openssl doesn't work. We have python module zlib to
decompress
the zlib data. zlib.decompress() should do the trick.
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-...@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
