From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, "Don A. Bailey" <donb@securitymouse.com>
Subject: [GIT PULL] Compression patches for 3.18-rc1
Date: Tue, 7 Oct 2014 15:33:28 -0700 [thread overview]
Message-ID: <20141007223328.GA5588@kroah.com> (raw)
The following changes since commit 9e82bf014195d6f0054982c463575cdce24292be:
Linux 3.17-rc5 (2014-09-14 17:50:12 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/compress-3.18-rc1
for you to fetch changes up to 72cf90124e87d975d0b2114d930808c58b4c05e4:
lzo: check for length overrun in variable length encoding. (2014-09-28 11:08:01 +0200)
----------------------------------------------------------------
Compression patches for 3.18-rc1
More fun with the LZO compression code. Here's some patches that
properly document what the logic is, and fix up all of the previously
reported issues against the LZO code.
This has been in linux-next for a while with no issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Willy Tarreau (3):
Documentation: lzo: document part of the encoding
Revert "lzo: properly check for overruns"
lzo: check for length overrun in variable length encoding.
Documentation/lzo.txt | 164 ++++++++++++++++++++++++++++++++++++++++
lib/lzo/lzo1x_decompress_safe.c | 103 ++++++++++++++-----------
2 files changed, 221 insertions(+), 46 deletions(-)
create mode 100644 Documentation/lzo.txt
reply other threads:[~2014-10-07 22:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141007223328.GA5588@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=donb@securitymouse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).