From: "Jan Beulich" <JBeulich@suse.com>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: <stable@kernel.org>, "Don A. Bailey" <donb@securitymouse.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] lz4: add overrun checks to lz4_uncompress_unknownoutputsize()
Date: Fri, 04 Jul 2014 07:12:56 +0100 [thread overview]
Message-ID: <53B662080200007800020831@mail.emea.novell.com> (raw)
In-Reply-To: <20140703231103.GA4081@kroah.com>
>>> On 04.07.14 at 01:11, <gregkh@linuxfoundation.org> wrote:
> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> Jan points out that I forgot to make the needed fixes to the
> lz4_uncompress_unknownoutputsize() function to mirror the changes done
> in lz4_decompress() with regards to potential pointer overflows.
Except that meanwhile Don agreed with my statement that neither
this nor the two earlier patches really fix the issue. So rather than
pushing this into 3.16 and stable trees, I wonder whether the two
earlier ones shouldn't be reverted and then a clean and correct
fix be applied.
Jan
next prev parent reply other threads:[~2014-07-04 6:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 23:11 Greg KH
2014-07-04 6:12 ` Jan Beulich [this message]
2014-07-04 13:01 ` Jan Beulich
2014-07-25 6:00 ` Jan Beulich
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=53B662080200007800020831@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=donb@securitymouse.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 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®