linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Aruna Balakrishnaiah <aruna@linux.vnet.ibm.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "jkenisto@linux.vnet.ibm.com" <jkenisto@linux.vnet.ibm.com>,
	Kees Cook <keescook@chromium.org>,
	"mahesh@linux.vnet.ibm.com" <mahesh@linux.vnet.ibm.com>,
	Colin Cross <ccross@android.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
	"paulus@samba.org" <paulus@samba.org>,
	Anton Blanchard <anton@samba.org>,
	Anton Vorontsov <cbouatmailru@gmail.com>
Subject: Re: [PATCH 3/3] powerpc/pseries: Support compression of oops text via pstore
Date: Thu, 27 Jun 2013 15:12:20 +0530	[thread overview]
Message-ID: <51CC08FC.6000301@linux.vnet.ibm.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31C5376F@ORSMSX106.amr.corp.intel.com>

Hi Tony,

On Tuesday 25 June 2013 09:32 PM, Luck, Tony wrote:
>> Introducing headersize in pstore_write() API would need changes at
>> multiple places whereits being called. The idea is to move the
>> compression support to pstore infrastructure so that other platforms
>> could also make use of it.
> Any thoughts on the back/forward compatibility as we switch to compressed
> pstore data?   E.g. imagine I have a system installed with some Linux distribution
> with a kernel too old to know about compressed pstore. I use that machine to
> run the latest kernels that do compression ... and one fine day one of them crashes
> hard - logging in compressed form to pstore. Now I boot my distro kernel to pick
> up the pieces ... what do I see in /sys/fs/pstore/*? Some compressed files? Can I
> read them with some tool?
>
> This somewhat of a corner case - but not completely unrealistic ... I'd at least
> like to be reassured that the old kernel won't choke when it sees the compressed
> blobs.

openssl command line tool can be used to decompress the compressed data of
the pstore file in the above scenario.

Usage:

cat <file> | openssl zlib -d

> -Tony
>

  reply	other threads:[~2013-06-27  9:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24  6:22 [RESEND PATCH 0/3] Nvram-to-pstore: compression support for oops data Aruna Balakrishnaiah
2013-06-24  6:22 ` [PATCH 1/3] Retreive header size from pstore Aruna Balakrishnaiah
2013-06-24  6:23 ` [PATCH 2/3] powerpc/pseries: Re-organise the oops compression code Aruna Balakrishnaiah
2013-06-24  6:23 ` [PATCH 3/3] powerpc/pseries: Support compression of oops text via pstore Aruna Balakrishnaiah
2013-06-24 17:57   ` Kees Cook
2013-06-25  7:04     ` Aruna Balakrishnaiah
2013-06-25 16:02       ` Luck, Tony
2013-06-27  9:42         ` Aruna Balakrishnaiah [this message]
2013-06-25 16:55       ` Kees Cook
  -- strict thread matches above, loose matches on Subject: below --
2013-04-26  9:55 [RFC PATCH 0/3] Nvram-to-pstore: compression support for oops data Aruna Balakrishnaiah
2013-04-26  9:56 ` [PATCH 3/3] powerpc/pseries: Support compression of oops text via pstore Aruna Balakrishnaiah
2013-06-01  4:54   ` Benjamin Herrenschmidt
2013-06-04  9:07     ` Aruna Balakrishnaiah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51CC08FC.6000301@linux.vnet.ibm.com \
    --to=aruna@linux.vnet.ibm.com \
    --cc=anton@samba.org \
    --cc=cbouatmailru@gmail.com \
    --cc=ccross@android.com \
    --cc=jkenisto@linux.vnet.ibm.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mahesh@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).