All of lore.kernel.org
 help / color / mirror / Atom feed
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 12:00:20 -0400	[thread overview]
Message-ID: <20140628160020.GA11019@kroah.com> (raw)
In-Reply-To: <CALWnrFRO_trdJ7aL_vaWtFbdJgxRkt4+zROR_chQFNPz7v3BVQ@mail.gmail.com>

On Sat, Jun 28, 2014 at 09:19:34PM +0530, Kiran Kankipati wrote:
> Hi Something similar to that I got inconsistency issue in LZ4-HC in 64bit mode.
> 
> I posted today in kernel bugzee:  https://bugzilla.kernel.org/show_bug.cgi?id=79091

I don't do bugzilla :)

Let's drag this back to lkml as well...

Ok, where do you see an overrun happening?  I know the lz4 code in the
kernel is "old" compared to upstream.  I am working on updating it to
the latest version, but that's not going to happen until 3.17.

In the mean time, did you note the lz4 patch that was merged yesterday,
it is commit id 4148c1f67abf823099b2d7db6851e4aea407f5ee in Linus's
tree.  Does that solve the issue you are seeing?

If not, do you have a data stream I can use to try to find and fix this?

thanks,

greg k-h

       reply	other threads:[~2014-06-28 16:00 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 ` Greg Kroah-Hartman [this message]
     [not found]   ` <CALWnrFRQ_VHzPtBe04n3xfeQu=kjw=TE+wotzyoTW5P6gdZ-zQ@mail.gmail.com>
2014-06-28 16:20     ` Bug in Kernel's LZ4-HC in 64bit (kernel crypto library) Greg Kroah-Hartman
     [not found]       ` <CALWnrFQJX2JBssSQ-CdYbcewjbTna=xKS4GRmJ4fHaactwERmg@mail.gmail.com>
2014-06-28 17:36         ` Greg Kroah-Hartman

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=20140628160020.GA11019@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.