All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@crca.org.au>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-crypto@vger.kernel.org,
	TuxOnIce Devel List <tuxonice-devel@lists.tuxonice.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: LZO irreversible output?
Date: Thu, 04 Feb 2010 15:37:27 +1100	[thread overview]
Message-ID: <4B6A4F07.3090509@crca.org.au> (raw)
In-Reply-To: <201002032354.11284.rjw@sisk.pl>

Hi Rafael.

Rafael J. Wysocki wrote:
> On Wednesday 03 February 2010, Nigel Cunningham wrote:
>> Hi all.
>>
>> (Not sent to LKML yesterday; no reply from linux-crypto yet, so resending).
>>
>> A while back now, I stopped supplying the LZF compression algorithm with
>> TuxOnIce and made LZO the default algorithm. Around the same time, we
>> started getting occasional errors when reading images; decompression
>> failures.
>>
>> I've finally managed to find the time to properly look at this, and have
>> managed to find a data page that LZO compresses, but seems to be unable
>> to decompress back to the original contents. I'm wondering whether this
>> is because I'm doing something wrong, or because there really is some
>> data the LZO (or the kernel implementation) can't do reversible
>> compression on.
> 
> Well, FWIW, we have never had any problems with the userland LZO in s2disk,
> so if anything is wrong with LZO here, I guess it's the kernel code.

Okay. Guess I have to start shipping LZF again and make it the default
again then.

Regards,

Nigel

  reply	other threads:[~2010-02-04  4:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 21:38 LZO irreversible output? Nigel Cunningham
2010-02-03 22:54 ` Rafael J. Wysocki
2010-02-04  4:37   ` Nigel Cunningham [this message]
2010-02-07 22:23     ` Bill Davidsen
2010-02-08  8:33       ` Nigel Cunningham
2010-02-09 17:32         ` Nix
2010-02-09 17:32           ` [TuxOnIce-devel] " Nix
2010-02-09 20:38           ` Nigel Cunningham
  -- strict thread matches above, loose matches on Subject: below --
2010-02-03  2:11 Nigel Cunningham

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=4B6A4F07.3090509@crca.org.au \
    --to=ncunningham@crca.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=tuxonice-devel@lists.tuxonice.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.