From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kiran Kankipati <kiran.kankipati@gmail.com>
Cc: "Don A. Bailey" <donb@securitymouse.com>, linux-kernel@vger.kernel.org
Subject: Re: Bug in Kernel's LZ4-HC in 64bit (kernel crypto library)
Date: Sat, 28 Jun 2014 13:36:36 -0400 [thread overview]
Message-ID: <20140628173636.GA6664@kroah.com> (raw)
In-Reply-To: <CALWnrFQJX2JBssSQ-CdYbcewjbTna=xKS4GRmJ4fHaactwERmg@mail.gmail.com>
On Sat, Jun 28, 2014 at 10:02:19PM +0530, Kiran Kankipati wrote:
> I don't understand, are you having problems on the compress side, or the
> decompress side? Where in the lz4 is a bug happening?
> >> Sorry sorry.
> I dont have a clue. Well the reason is, if compress is happening well and
> decomp is getting this issue. Then decomp is having a bug.
> If compression is corrupting data, then decomp may get this issue too. Hence I
> am not fully sure.
> But the error code happening in the decomp API.
>
>
> Do you have a data stream that I can use to run it through the lz4 code
> to see where the problem is in the compress/decompress code?
> >> Again sorry about it. Since iam testing with real-time packets. I dont have
> it Greg.
>
> I can copypaste the error logs of my TrafficSqueezer per-packet tests. Since I
> am running a simulation test, I am doing each packet
> compression + decompression. This way I can test TrafficSqueezer stack. As well
> in our case we can test LZ4 too.
>
> Kindly refer screenshot:
>
> But please note, sometimes it works fine too. Sometimes I am getting this error
> :(
>
> Its purely LZ4-HC error. Since the return code of
> lz4_decompress_unknownoutputsize() API is <0 i.e error !
As you are compressing and then decompressing, this doesn't look to be
the same "type" of error we have fixed recently, so I don't know what to
do here.
If you find a data stream that this can be tested with, please let me
know and I'll be glad to try it out. Until then, I need more of a hint
as to the problem before I can do anything, sorry.
greg k-h
prev parent reply other threads:[~2014-06-28 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALWnrFRO_trdJ7aL_vaWtFbdJgxRkt4+zROR_chQFNPz7v3BVQ@mail.gmail.com>
2014-06-28 16:00 ` Bug in Kernel's LZ4-HC in 64bit (kernel crypto library) Greg Kroah-Hartman
[not found] ` <CALWnrFRQ_VHzPtBe04n3xfeQu=kjw=TE+wotzyoTW5P6gdZ-zQ@mail.gmail.com>
2014-06-28 16:20 ` Greg Kroah-Hartman
[not found] ` <CALWnrFQJX2JBssSQ-CdYbcewjbTna=xKS4GRmJ4fHaactwERmg@mail.gmail.com>
2014-06-28 17:36 ` Greg Kroah-Hartman [this message]
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=20140628173636.GA6664@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=donb@securitymouse.com \
--cc=kiran.kankipati@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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.