All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: paulus@samba.org, marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zlib double-free bug
Date: Mon, 18 Mar 2002 08:15:26 -0700	[thread overview]
Message-ID: <20020318151526.GD3762@opus.bloom.county> (raw)
In-Reply-To: <15509.51214.495427.580341@argo.ozlabs.ibm.com> <20020318144946.GA7052@werewolf.able.es>

On Mon, Mar 18, 2002 at 03:49:46PM +0100, J.A. Magallon wrote:
 
> The only rest it leaves in 19-pre3 are:
> 
> ./arch/ppc/boot/lib/zlib.c
> ./arch/ppc/boot/include/zlib.h
> 
> Patch already does:
> 
> --- linux-2.4.19-pre2-ac2/arch/ppc/config.in    Sun Mar  3 18:54:31 2002
> +++ linux-2.4.19-pre2-ac2-zlib/arch/ppc/config.in   Tue Mar  5 08:57:31 2002
> @@ -396,6 +396,8 @@
>     source net/bluetooth/Config.in
>  fi
>  
> +source lib/Config.in
> +  
>  mainmenu_option next_comment
>  comment 'Kernel hacking'
>  
> 
> So wouldn't it be better to kill ppc/.../zlib and make it use also the
> shared copy ?

Not really.  The arch/ppc/boot version (and arch/mips/boot'ish too, when
it gets merged) are slightly different from the in-kernel ones by ~1
line, so that they allow things to be decompressed to 0x0.  My plan for
2.5 is to get the PPC version using the lib/zlib_deflate stuff (by dummy
files doing #include too), maybe.  But either way it's a non-issue (if
you can't trust the 'zImage' binary, you've got bigger problems than
someone trying to expliot a bug before Linux is running).

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

  reply	other threads:[~2002-03-18 15:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18 10:57 [PATCH] zlib double-free bug Paul Mackerras
2002-03-18 14:49 ` J.A. Magallon
2002-03-18 15:15   ` Tom Rini [this message]
2002-03-18 16:36   ` David Woodhouse
2002-03-18 22:09     ` Paul Mackerras
2002-03-19 10:45       ` David Woodhouse
2002-03-19 13:53         ` David Woodhouse
2002-03-19 18:06         ` H. Peter Anvin
2002-03-19 19:14           ` Dave Jones
2002-03-19 19:36             ` H. Peter Anvin
2002-03-19 19:50               ` Dave Jones
2002-03-19 19:59                 ` H. Peter Anvin
2002-03-19 20:09                   ` Dave Jones
2002-03-19 20:35           ` Nicolas Pitre
2002-03-20  9:45             ` Helge Hafting
2002-03-20 14:45               ` Nicolas Pitre
2002-03-21 20:14                 ` H. Peter Anvin
2002-03-21 21:03                   ` Tom Rini
2002-03-21 21:21                     ` Tom Rini
2002-03-21 22:13                     ` Alan Cox
2002-03-22  0:06                       ` Corey Minyard
2002-03-22  7:26                         ` David Woodhouse
2002-03-20 15:59               ` Martin Hermanowski
2002-03-20 16:17                 ` Tom Rini
2002-03-19  5:01 ` Paul Mackerras

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=20020318151526.GD3762@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=paulus@samba.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.