From: Corey Minyard <minyard@acm.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tom Rini <trini@kernel.crashing.org>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zlib double-free bug
Date: Thu, 21 Mar 2002 18:06:37 -0600 [thread overview]
Message-ID: <3C9A758D.103@acm.org> (raw)
In-Reply-To: <E16oAoJ-0006RH-00@the-village.bc.nu>
Alan Cox wrote:
>>It's getting there. The 'issue' is that the best way to fix it (maybe
>>2.4.20-pre1 even) is to backport the 2.5 zlib which doesn't have this
>>
>
>2.4.19ac has the shared zlib already. The zlib sharing stuff wasnt a 2.5
>patch backported - its a 2.4 fix that went forward
>
Since I did the original shared zlib patch and I did it to 2.5, either
we have two patches floating around or you are incorrect. If we have
two patches, we need to resolve the situation.
-Corey
next prev parent reply other threads:[~2002-03-22 0:11 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
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 [this message]
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=3C9A758D.103@acm.org \
--to=minyard@acm.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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.