From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Nitin Gupta" <nitingupta910@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Richard Purdie" <richard@openedhand.com>
Subject: Re: [RFC] LZO1X de/compression support
Date: Fri, 18 May 2007 23:14:57 +0200 [thread overview]
Message-ID: <m3646pg7fy.fsf@maximus.localdomain> (raw)
In-Reply-To: <4cefeab80705180258g516a6f92w15a49e666dd62b66@mail.gmail.com> (Nitin Gupta's message of "Fri, 18 May 2007 15:28:31 +0530")
"Nitin Gupta" <nitingupta910@gmail.com> writes:
> Facts for LZO (at least for original code. Should hold true for this
> port also - hence the RFC!):
> - The compressor can never overrun buffer.
> - The "non-safe" version of decompressor can never overrun buffer if
> compressed data is unmodified. I am not sure about this if compressed
> data is malicious (to be confirmed from the author).
> - The "safe" version can never crash (buffer overrun etc.) - confirmed
> from the author.
I'm certainly missing something but what are the advantages of this
code (over current gzip etc.), and what will be using it?
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-05-18 21:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 9:58 Nitin Gupta
2007-05-18 10:14 ` Heikki Orsila
2007-05-18 11:27 ` Nitin Gupta
2007-05-18 11:53 ` Richard Purdie
2007-05-18 10:42 ` Pekka Enberg
2007-05-18 10:53 ` Pekka Enberg
2007-05-22 8:54 ` Nitin Gupta
2007-05-22 8:59 ` Pekka Enberg
2007-05-22 9:10 ` Nitin Gupta
2007-05-22 9:34 ` Pekka Enberg
2007-05-18 11:11 ` Andrey Panin
2007-05-22 9:08 ` Nitin Gupta
2007-05-22 19:44 ` Jan Engelhardt
2007-05-22 21:24 ` Bernd Petrovitsch
2007-05-23 16:35 ` Jeremy Fitzhardinge
2007-05-18 11:46 ` Richard Purdie
2007-05-22 9:19 ` Nitin Gupta
2007-05-18 20:04 ` Matt Mackall
2007-05-18 21:14 ` Krzysztof Halasa [this message]
2007-05-19 18:55 ` Bill Rugolsky Jr.
2007-05-19 21:52 ` Richard Purdie
2007-05-22 19:40 ` Jan Engelhardt
2007-05-19 18:12 devzero
2007-05-20 11:42 Tomasz Chmielewski
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=m3646pg7fy.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nitingupta910@gmail.com \
--cc=richard@openedhand.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
Powered by JetHome