public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Sorber <aafes@psu.edu>
To: Chris Chabot <chabotc@reviewboard.com>
Cc: Florian Weimer <Florian.Weimer@RUS.Uni-Stuttgart.DE>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Severe Linux 2.4 kernel memory leakage
Date: 25 Nov 2001 10:41:57 -0500	[thread overview]
Message-ID: <1006702918.3088.3.camel@praetorian> (raw)
In-Reply-To: <1006702226.1316.2.camel@gandalf.chabotc.com>
In-Reply-To: <1006699767.1178.0.camel@gandalf.chabotc.com>  <tgy9kuevtw.fsf@mercury.rus.uni-stuttgart.de>  <1006702226.1316.2.camel@gandalf.chabotc.com>

[-- Attachment #1: Type: text/plain, Size: 304 bytes --]

On Sun, 2001-11-25 at 10:30, Chris Chabot wrote:
> The kernel i ran for about a month was kernel 2.4.11.
> 

wasn't kernel 2.4.11 labeled "dontuse"?

that had a serious bug in it.

> 
-- 
Phil Sorber
AIM: PSUdaemon
IRC: irc.openprojects.net #psulug PSUdaemon
GnuPG: keyserver - pgp.mit.edu

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-11-25 15:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-25 14:49 Severe Linux 2.4 kernel memory leakage Chris Chabot
2001-11-25 15:03 ` Florian Weimer
2001-11-25 15:30   ` Chris Chabot
2001-11-25 15:41     ` Phil Sorber [this message]
2001-11-25 15:51       ` Chris Chabot
2001-11-25 17:17         ` Phil Sorber
2001-11-25 18:44           ` Chris Chabot
2001-11-25 15:53       ` François Cami
2001-11-25 15:55     ` Mr. Shannon Aldinger
2001-11-25 16:14       ` Florian Weimer
2001-11-26 15:11       ` Christoph Rohland
2001-11-25 15:10 ` James Morris
2001-11-25 15:19   ` Chris Chabot
2001-11-25 15:27 ` Peter T. Breuer
2001-11-25 15:39   ` Chris Chabot
2001-11-25 17:03   ` Andi Kleen
2001-11-26 20:15     ` Bill Davidsen
2001-11-26  6:49 ` Mike Galbraith
2001-11-26  9:50   ` Chris Chabot

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=1006702918.3088.3.camel@praetorian \
    --to=aafes@psu.edu \
    --cc=Florian.Weimer@RUS.Uni-Stuttgart.DE \
    --cc=chabotc@reviewboard.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