From: Dave Jones <davej@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zlib double-free bug
Date: Tue, 19 Mar 2002 21:09:16 +0100 [thread overview]
Message-ID: <20020319210916.M19346@suse.de> (raw)
In-Reply-To: <15510.25987.233438.112897@argo.ozlabs.ibm.com> <Pine.LNX.4.44.0203191044150.26226-100000@passion.cambridge.redhat.com> <a77umb$t3s$1@cesium.transmeta.com> <20020319201427.K19346@suse.de> <3C979333.6020500@zytor.com> <20020319205029.L19346@suse.de> <3C97988B.1030401@zytor.com>
On Tue, Mar 19, 2002 at 11:59:07AM -0800, H. Peter Anvin wrote:
> > My understanding from one of dwmw2's earlier posts was that jffs2
> > has crc's that would prevent this happening anyway (or at least make
> > it nigh on impossible)
> I doubt that. We're talking about corrupting the kernel VM.
Ignore me, I'm losing my mind.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-03-19 20:09 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 [this message]
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=20020319210916.M19346@suse.de \
--to=davej@suse.de \
--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).