[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200705291614.34504.dhazelton@enter.net>
Date: Tue, 29 May 2007 16:14:34 -0400
From: Daniel Hazelton <dhazelton@...er.net>
To: "Nitin Gupta" <nitingupta910@...il.com>
Cc: "Bret Towe" <magnade@...il.com>,
lkml <linux-kernel@...r.kernel.org>, linux-mm-cc@...top.org,
linuxcompressed-devel@...ts.sourceforge.net,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Richard Purdie" <richard@...nedhand.com>,
"Satyam Sharma" <satyam.sharma@...il.com>
Subject: Re: [RFC] LZO de/compression support - take 6
On Tuesday 29 May 2007 01:58:43 Nitin Gupta wrote:
> On 5/29/07, Bret Towe <magnade@...il.com> wrote:
> > tested this on ppc and its still good
> >
> > is there any reason to bother with a test on amd64?
> > if there is I might be able to get to it tonight
>
> Yes, this test is desired on 'take 6'
> (In future I will append version to patch bz2)
>
> Thanks,
> Nitin
I added a few functions to my test-bed to see how well the LZO code coped with
random input data. I'll extend my error checking so that it dumps all local
variables at the first error, but for the time being I'm staring at a problem
with what appears to be a double-free (in addition to lzo1x_decompress(_safe)
screaming about overruns when I pass it the buffer of compressed, totally
random data).
(I fill the buffer by doing a read from /dev/urandom, though I'll certainly
change it to use random() if anyone thinks that'll make a difference)
I'll post the version with the random-data tests when I get the double-free
solved. (I've looked and don't see how its happening)
DRH
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists