From: Tom Rini <trini@kernel.crashing.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zlib double-free bug
Date: Thu, 21 Mar 2002 14:03:56 -0700 [thread overview]
Message-ID: <20020321210356.GI25237@opus.bloom.county> (raw)
In-Reply-To: <3C985A46.D3C73301@aitel.hist.no> <Pine.LNX.4.44.0203200943230.3615-100000@xanadu.home> <a7dev9$n51$1@cesium.transmeta.com>
On Thu, Mar 21, 2002 at 12:14:33PM -0800, H. Peter Anvin wrote:
> Followup to: <Pine.LNX.4.44.0203200943230.3615-100000@xanadu.home>
> By author: Nicolas Pitre <nico@cam.org>
> In newsgroup: linux.dev.kernel
> >
> > On Wed, 20 Mar 2002, Helge Hafting wrote:
> >
> > > Nicolas Pitre wrote:
> > >
> > > > > Removable media?
> > > >
> > > > Most if not all removable media are not ment to be used with JFFS2.
> > >
> > > Nothing is _meant_ to be exploited either. Someone could
> > > create a cdrom with jffs2 (linux don't demand that cd's use iso9660)
> >
> > But JFFS2 demands to be used with AN MTD device, not a block device. And
> > most MTD device, if not all of them, on which JFFS2 is used aren't
> > removable.
>
> Isn't this whole discussion a bit silly? If I'm not mistaken, we're
> talking about a one-line known fix here...
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
problem and removes most of the copies of zlib from the kernel. If it's
not really a problem now, why fix it? (Tho it should be a safe fix now
that Paul has produced a patch which doesn't suffer from random oopses
or other problems).
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2002-03-21 21:08 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 [this message]
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=20020321210356.GI25237@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=hpa@zytor.com \
--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;
as well as URLs for NNTP newsgroup(s).