From: Andrew Morton <akpm@linux-foundation.org>
To: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] inflate_fast: sout is already a short so ptr arith was off by one.
Date: Tue, 2 Mar 2010 14:52:31 -0800 [thread overview]
Message-ID: <20100302145231.5f3f0fb0.akpm@linux-foundation.org> (raw)
In-Reply-To: <1267373163-10841-1-git-send-email-Joakim.Tjernlund@transmode.se>
On Sun, 28 Feb 2010 17:06:02 +0100
Joakim Tjernlund <Joakim.Tjernlund@transmode.se> wrote:
> This won't change anything for current code, but post increment
> will break without this fix, should anyone want to try that.
>
The description is a bit cryptic. Hopefully you understand what you
mean, but does anyone else?
> diff --git a/lib/zlib_inflate/inffast.c b/lib/zlib_inflate/inffast.c
> index fa62fc7..2c13ecc 100644
> --- a/lib/zlib_inflate/inffast.c
> +++ b/lib/zlib_inflate/inffast.c
> @@ -286,7 +286,7 @@ void inflate_fast(z_streamp strm, unsigned start)
> } else { /* dist == 1 or dist == 2 */
> unsigned short pat16;
>
> - pat16 = *(sout-2+2*OFF);
> + pat16 = *(sout-1+OFF);
> if (dist == 1) {
> union uu mm;
> /* copy one char pattern to both bytes */
The code you're altering was changed two months ago by, err, you. I
don't know if the patch still makes sense in current kernels.
Please don't raise patches against old kernels. Please check that,
redo the patch, add a changelog which helps non-inffast.c people
understand what it does, then resend?
next prev parent reply other threads:[~2010-03-02 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 16:06 [PATCH 1/2] inflate_fast: sout is already a short so ptr arith was off by one Joakim Tjernlund
2010-02-28 16:06 ` [PATCH 2/2] crc32: Some minor cleanups Joakim Tjernlund
2010-03-02 22:52 ` Andrew Morton [this message]
2010-03-03 7:35 ` [PATCH 1/2] inflate_fast: sout is already a short so ptr arith was off by one Joakim Tjernlund
[not found] ` <20100302234217.9eaa7c5e.akpm@linux-foundation.org>
2010-03-03 11:35 ` Joakim Tjernlund
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=20100302145231.5f3f0fb0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Joakim.Tjernlund@transmode.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox