From: "Nitin Gupta" <nitingupta910@gmail.com>
To: "Michael-Luke Jones" <mlj28@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org,
"Richard Purdie" <richard@openedhand.com>,
linux-mm-cc@laptop.org
Subject: Re: [RFC] LZO de/compression support - take 3
Date: Wed, 23 May 2007 17:09:46 +0530 [thread overview]
Message-ID: <4cefeab80705230439n6bbb1259le3c3b9704ce49b75@mail.gmail.com> (raw)
In-Reply-To: <0F6CEFD7-86F2-4903-B4F7-F723DF88BE9A@cam.ac.uk>
Hi Michael,
On 5/23/07, Michael-Luke Jones <mlj28@cam.ac.uk> wrote:
> On 23 May 2007, at 09:27, Nitin Gupta wrote:
>
> > This contains LZO1X-1 compressor and LZO1X decompressor (safe and
> > standard version).
>
> I understand that the 'safe' decompression code is 'somewhat slower'
> and that decompressor performance is a key feature of this algorithm.
> However, I am concerned about the safety implications of including
> the 'unsafe' standard version in-kernel when likely uses include
> compression of network data, memory objects and so-on, all of which
> could in theory be maliciously modified.
>
The 'unsafe' version is still included since in some scenarios we have
guarantee that compressed data has not been modified (for e.g. where
we keep compressed data in memory only). So, in those cases there is
no need to go for slower 'safe' version. So, the version of
decompressor selected should be left to the user (kernel dev) only -
he should make sure that he is using the right version.
Cheers,
Nitin
next prev parent reply other threads:[~2007-05-23 11:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 8:27 Nitin Gupta
2007-05-23 10:53 ` Michael-Luke Jones
2007-05-23 11:39 ` Nitin Gupta [this message]
2007-05-23 13:57 ` Michael-Luke Jones
2007-05-23 14:03 ` Nitin Gupta
2007-05-23 14:10 ` Michael-Luke Jones
2007-05-23 14:21 ` Nitin Gupta
2007-05-23 14:33 ` Michael-Luke Jones
2007-05-24 22:41 ` Richard Purdie
2007-05-24 22:54 ` Andrew Morton
2007-05-24 23:00 ` Richard Purdie
2007-05-23 16:16 ` Andrew Morton
2007-05-23 16:49 ` Richard Purdie
2007-05-24 4:04 ` Nitin Gupta
2007-05-25 10:42 ` Pavel Machek
2007-05-26 10:23 ` Michael-Luke Jones
2007-05-26 11:17 ` Nitin Gupta
2007-05-23 14:50 ` Bret Towe
2007-05-24 13:48 ` Nitin Gupta
2007-05-25 2:38 ` Bret Towe
2007-05-25 5:10 ` Nitin Gupta
2007-05-25 17:02 ` Bret Towe
2007-05-25 17:33 ` Nitin Gupta
2007-05-26 11:30 ` Nitin Gupta
2007-05-27 3:39 ` Bret Towe
2007-05-23 19:34 ` Satyam Sharma
2007-05-24 4:37 ` Nitin Gupta
2007-05-24 10:49 ` Satyam Sharma
2007-05-24 8:25 ` Richard Purdie
2007-05-24 11:07 ` Satyam Sharma
2007-05-24 14:29 ` Nitin Gupta
2007-05-24 19:12 ` Satyam Sharma
2007-05-24 14:20 ` Nitin Gupta
2007-05-24 20:09 ` Satyam Sharma
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=4cefeab80705230439n6bbb1259le3c3b9704ce49b75@mail.gmail.com \
--to=nitingupta910@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm-cc@laptop.org \
--cc=mlj28@cam.ac.uk \
--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
all inboxes | Powered by JetHome®