mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Dow, Benjamin" <bdow@itouchcom.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'Rik van Riel'" <riel@conectiva.com.br>
Subject: Re: kernel memory leak?
Date: Wed, 9 Oct 2002 00:54:00 +0200	[thread overview]
Message-ID: <20021008225400.GA889@elf.ucw.cz> (raw)
In-Reply-To: <19EE6EC66973A5408FBE4CB7772F6F0A046A39@ltnmail.xyplex.com>

Hi!

> I sent this out yesterday, and never got a reply.  Normally, I'd be far more
> patient, but I'm afraid that by now people have forgotten about it, and I'm
> under a LOT of pressure by management to get this fixed soon.
> 
> To recap my previous e-mail, every time I access a file, 4k of memory gets
> allocated, and never gets freed, to the point of eventually triggering the
> OOM killer.  I don't know nearly enough about the VM to debug this myself,
> so even a pointer to where to start looking would be helpful.

Write C code to reproduce this on normal machine, and post it to
bugtraq (its DoS, after all). Pretty aggresive but sure to get fixed
*fast*.

The same without going bugtraq should suffice, through.
									Pavel

-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org

  reply	other threads:[~2002-10-09  9:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 18:16 Dow, Benjamin
2002-10-08 22:54 ` Pavel Machek [this message]
2002-10-11  8:54   ` Nicholas Hockey
2002-10-11  8:58   ` Nicholas Hockey
  -- strict thread matches above, loose matches on Subject: below --
2006-07-17 16:53 Kernel " Andreas Rieke
2006-07-17 18:28 ` Michal Piotrowski
2002-10-10 18:09 kernel " Dow, Benjamin
2002-10-10 16:31 Manfred Spraul
2002-10-10 14:32 Dow, Benjamin
2002-10-07 21:58 Dow, Benjamin

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=20021008225400.GA889@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=bdow@itouchcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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

all inboxes | Powered by JetHome®