From: Henrik Storner <henrik-kernel@hswn.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-18 size-4096 memory leaks
Date: Wed, 26 Nov 2003 10:11:15 +0000 (UTC) [thread overview]
Message-ID: <bq1u83$pcu$1@ask.hswn.dk> (raw)
In-Reply-To: BAY2-F65DwLK4adtttY00010f98@hotmail.com
In <BAY2-F65DwLK4adtttY00010f98@hotmail.com> "yuval yeret" <yuval_yeret@hotmail.com> writes:
>I'm seeing a constant leak in size-4096 on a machine running 2.4.20-18 SMP
>BIGMEM, which might / might not be related to the machine finally going out
>of memory and going into a hang.
This sounds like one of the Red Hat kernels - those are immensely
patched and very different from the original Linux kernels normally
discussed here.
However ...
>I saw a discussion around similar problems in 2.6.0 (2.6.0-test5/6 (and
>probably 7 too) size-4096 memory leak - http://lkml.org/lkml/2003/10/17/5 )
>and an ext3 patch was suggested by Andrew Morton.
>From a brief look the code in 2.4 it seems like the patch might be relevant
>here as well. Is the size-4096 leak a known issue for 2.4 ?
>Is the 2.6 patch applicable in 2.4 as well ?
There definitely is a memory leak in the Red Hat 9 kernels, including
the 2.4.20-20.9smp kernel (seems to be in the uniprocessor build as well).
It leaks mm_struct slabs - see the trend graphs I do from the slabinfo
data, available at
http://tyge.sslug.dk/bb-cgi/larrd-grapher.cgi?host=tyge.sslug.dk&service=slabinfo
The blue curve is the mm_struct slab allocation (column 5, the "active
pages" column from /proc/slabinfo) - the way it continually grows from
the system is rebooted IMHO points to a memory leak somewhere. This is
very clear from the third graph, which goes back the last 48 days,
during which we had two reboots of the system (hardware related).
The standard kernels from www.kernel.org do not have this problem,
so I am fairly certain it is in one of the Red Hat patches.
Others also see it:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=91090
Henrik
--
Henrik Storner <henrik@hswn.dk>
next prev parent reply other threads:[~2003-11-26 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 9:29 2.4.20-18 size-4096 memory leaks yuval yeret
2003-11-26 10:11 ` Henrik Storner [this message]
2003-11-26 11:51 ` Stephen C. Tweedie
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 10:24 yuval yeret
2003-11-26 10:57 Jean Delvare
2003-11-26 11:57 ` Stephen C. Tweedie
2003-11-26 14:14 yuval yeret
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='bq1u83$pcu$1@ask.hswn.dk' \
--to=henrik-kernel@hswn.dk \
--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 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.