LKML Archive on
help / color / mirror / Atom feed
From: Henrik Storner <>
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$> (raw)
In-Reply-To: <>

In <> "yuval yeret" <> 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 - )
>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

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 do not have this problem,
so I am fairly certain it is in one of the Red Hat patches.

Others also see it:

Henrik Storner <> 

  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 yuval yeret
2003-11-26 10:11 ` Henrik Storner [this message]
2003-11-26 11:51 ` Stephen C. Tweedie
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='bq1u83$pcu$' \ \ \
    --subject='Re: 2.4.20-18 size-4096 memory leaks' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).