All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas Hockey" <tilt@bitchx.org>
To: "Pavel Machek" <pavel@ucw.cz>, "Dow, Benjamin" <bdow@itouchcom.com>
Cc: <linux-kernel@vger.kernel.org>,
	"'Rik van Riel'" <riel@conectiva.com.br>, <'tilt@bitchx.org'>
Subject: Re: kernel memory leak?
Date: Fri, 11 Oct 2002 04:54:22 -0400	[thread overview]
Message-ID: <007601c27103$cb92c7b0$7b00a8c0@enigma> (raw)
In-Reply-To: 20021008225400.GA889@elf.ucw.cz

i am having a similar problem, i'm thinking somthing in the XFS software is
malloc()ing ram and not letting it go, by any chance are you using XFS ?
what i did was write this lil things to recover my ram,it eats ram till it's
killed effectivly recovering lost ram (i just had to include this)
---ayrabtu.c---
#include <stdio.h>
#include <stdlib.h>

int main(int argc, char *argv[]) {
        char *allyourram;
        char arebelongtous[] = "all your ram are belong to us";

        while (1) {
                allyourram = malloc(30);
                sprintf(allyourram, "%s", arebelongtous);
        }

        return(0);
}
---EOF---



  reply	other threads:[~2002-10-11  8:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 18:16 kernel memory leak? Dow, Benjamin
2002-10-08 22:54 ` Pavel Machek
2002-10-11  8:54   ` Nicholas Hockey [this message]
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='007601c27103$cb92c7b0$7b00a8c0@enigma' \
    --to=tilt@bitchx.org \
    --cc='tilt@bitchx.org' \
    --cc=bdow@itouchcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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 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.