The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alberto Bertogli <albertogli@telpin.com.ar>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test5/6 (and probably 7 too) size-4096 memory leak
Date: Wed, 15 Oct 2003 23:55:54 -0300	[thread overview]
Message-ID: <20031016025554.GH4292@telpin.com.ar> (raw)

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


Hi there!

I want to report a memory leak for 2.6.0-test5 that I've noticed today on
a mail server after 32 days of uptime.

As I'm upgrading it tomorrow to test7 I wasn't going to report this until
verifying if the behaviour continued, but I saw on kernelnewbies that
others were having this issue with test7 too, so I decided to post a
report with the information before I reboot the server.

The attached files are gzipped for space reasons, and were taken at night
when the server isn't very loaded.

The workload is a simple sendmail with ipop3d and imapd, nothing much, for
about 6500 users; the machine is a dual Pentium III with 1gb of RAM and a
couple of SCSI disks.

Slabinfo reports that size-4096 has 104341 active objects and growing.

On another box at home I see the same issue with test6, but "only" with
11612 objects; I'm not posting info on this box as I guess the mailserver
is much more important because the leak is really noticeable.


Please let me know if I can help with anything.

Thanks,
		Alberto


[-- Attachment #2: config.gz --]
[-- Type: application/x-gunzip, Size: 5843 bytes --]

[-- Attachment #3: cpuinfo.gz --]
[-- Type: application/x-gunzip, Size: 298 bytes --]

[-- Attachment #4: free.gz --]
[-- Type: application/x-gunzip, Size: 154 bytes --]

[-- Attachment #5: meminfo.gz --]
[-- Type: application/x-gunzip, Size: 287 bytes --]

[-- Attachment #6: prev_dmesg.gz --]
[-- Type: application/x-gunzip, Size: 5440 bytes --]

[-- Attachment #7: ps_auxfww.gz --]
[-- Type: application/x-gunzip, Size: 1655 bytes --]

[-- Attachment #8: slabinfo.gz --]
[-- Type: application/x-gunzip, Size: 2115 bytes --]

[-- Attachment #9: sysrq+t.gz --]
[-- Type: application/x-gunzip, Size: 8945 bytes --]

[-- Attachment #10: uname.gz --]
[-- Type: application/x-gunzip, Size: 98 bytes --]

[-- Attachment #11: uptime.gz --]
[-- Type: application/x-gunzip, Size: 94 bytes --]

[-- Attachment #12: vmstat_5.gz --]
[-- Type: application/x-gunzip, Size: 1546 bytes --]

             reply	other threads:[~2003-10-16  2:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16  2:55 Alberto Bertogli [this message]
2003-10-16  4:19 ` 2.6.0-test5/6 (and probably 7 too) size-4096 memory leak Andrew Morton
2003-10-16  4:43   ` William Lee Irwin III
2003-10-16  4:58     ` Andrew Morton
2003-10-16  5:40       ` Manfred Spraul
2003-10-16  6:31         ` Andrew Morton
2003-10-16 15:13           ` Manfred Spraul
2003-10-17  5:56 ` Andrew Morton

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=20031016025554.GH4292@telpin.com.ar \
    --to=albertogli@telpin.com.ar \
    --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