From: Wu Fengguang <fengguang.wu@intel.com>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"bugme-daemon@bugzilla.kernel.org"
<bugme-daemon@bugzilla.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [Bug 12832] New: kernel leaks a lot of memory
Date: Wed, 11 Mar 2009 15:14:45 +0800 [thread overview]
Message-ID: <20090311071445.GA13584@localhost> (raw)
In-Reply-To: <20090311075703.35de2488@mjolnir.ossman.eu>
On Wed, Mar 11, 2009 at 08:57:03AM +0200, Pierre Ossman wrote:
> On Wed, 11 Mar 2009 09:37:40 +0800
> Wu Fengguang <fengguang.wu@intel.com> wrote:
>
> >
> > This 80MB noflags pages together with the below 80MB lru pages are
> > very close to the missing page numbers :-) Could you run the following
> > commands on fresh booted 2.6.27 and post the output files? Thank you!
> >
> > dd if=/dev/zero of=/tmp/s bs=1M count=1 seek=1024
> > cp /tmp/s /dev/null
> >
> > ./page-flags > flags
> > ./page-areas =0x20000 > areas-noflags
> > ./page-areas =0x00020 > areas-lru
> >
>
> Attached.
Thank you very much!
> I have to say, the patterns look very much like some kind of leak.
Wow it looks really interesting. The lru pages and noflags pages make
perfect 1-page interleaved pattern...
Thanks,
Fengguang
areas-lru
> offset len KB
> 86016 1 4KB
> 86018 1 4KB
> 86020 1 4KB
> 86022 1 4KB
> 86024 1 4KB
> 86026 1 4KB
> 86028 1 4KB
> 86030 1 4KB
> 86032 1 4KB
> 86034 1 4KB
> 86036 1 4KB
> 86038 1 4KB
> 86040 1 4KB
> 86042 1 4KB
> 86044 1 4KB
> 86046 1 4KB
> 86048 1 4KB
> 86050 1 4KB
> 86052 1 4KB
> 86054 1 4KB
> 86056 1 4KB
> 86058 1 4KB
> 86060 1 4KB
> 86062 1 4KB
> 86064 1 4KB
> 86066 1 4KB
> 86068 1 4KB
> 86070 1 4KB
> 86072 1 4KB
> 86074 1 4KB
> 86076 1 4KB
> 86078 1 4KB
> 86080 1 4KB
> 86082 1 4KB
> 86084 1 4KB
> 86086 1 4KB
> 86088 1 4KB
> 86090 1 4KB
> 86092 1 4KB
> 86094 1 4KB
> 86096 1 4KB
> 86098 1 4KB
> 86100 1 4KB
> 86102 1 4KB
> 86104 1 4KB
areas-noflags
> 86017 1 4KB
> 86019 1 4KB
> 86021 1 4KB
> 86023 1 4KB
> 86025 1 4KB
> 86027 1 4KB
> 86029 1 4KB
> 86031 1 4KB
> 86033 1 4KB
> 86035 1 4KB
> 86037 1 4KB
> 86039 1 4KB
> 86041 1 4KB
> 86043 1 4KB
> 86045 1 4KB
> 86047 1 4KB
> 86049 1 4KB
> 86051 1 4KB
> 86053 1 4KB
> 86055 1 4KB
> 86057 1 4KB
> 86059 1 4KB
> 86061 1 4KB
> 86063 1 4KB
> 86065 1 4KB
> 86067 1 4KB
> 86069 1 4KB
> 86071 1 4KB
> 86073 1 4KB
> 86075 1 4KB
> 86077 1 4KB
> 86079 1 4KB
> 86081 1 4KB
> 86083 1 4KB
> 86085 1 4KB
> 86087 1 4KB
> 86089 1 4KB
> 86091 1 4KB
> 86093 1 4KB
> 86095 1 4KB
> 86097 1 4KB
> 86099 1 4KB
> 86101 1 4KB
> 86103 1 4KB
> flags page-count MB symbolic-flags long-symbolic-flags
> 0x00000 1892 7 __________________
> 0x00004 1 0 __R_______________ referenced
> 0x00008 454 1 ___U______________ uptodate
> 0x0000c 94 0 __RU______________ referenced,uptodate
> 0x00020 20576 80 _____l____________ lru
> 0x00028 226 0 ___U_l____________ uptodate,lru
> 0x0002c 67911 265 __RU_l____________ referenced,uptodate,lru
> 0x00068 6621 25 ___U_lA___________ uptodate,lru,active
> 0x0006c 1222 4 __RU_lA___________ referenced,uptodate,lru,active
> 0x00078 1 0 ___UDlA___________ uptodate,dirty,lru,active
> 0x00080 3523 13 _______S__________ slab
> 0x000c0 55 0 ______AS__________ active,slab
> 0x00228 5 0 ___U_l___x________ uptodate,lru,reclaim
> 0x0022c 1 0 __RU_l___x________ referenced,uptodate,lru,reclaim
> 0x00268 23 0 ___U_lA__x________ uptodate,lru,active,reclaim
> 0x0026c 52 0 __RU_lA__x________ referenced,uptodate,lru,active,reclaim
> 0x00400 9 0 __________B_______ buddy
> 0x00408 60 0 ___U______B_______ uptodate,buddy
> 0x00800 4042 15 ___________r______ reserved
> 0x04020 9 0 _____l________P___ lru,private
> 0x04024 14 0 __R__l________P___ referenced,lru,private
> 0x04028 4 0 ___U_l________P___ uptodate,lru,private
> 0x0402c 1 0 __RU_l________P___ referenced,uptodate,lru,private
> 0x04060 10 0 _____lA_______P___ lru,active,private
> 0x04064 7 0 __R__lA_______P___ referenced,lru,active,private
> 0x04068 16 0 ___U_lA_______P___ uptodate,lru,active,private
> 0x20000 24227 94 _________________n noflags
> total 131056 511
> MemTotal: 508056 kB
> MemFree: 7716 kB
> Buffers: 220 kB
> Cached: 280468 kB
> SwapCached: 0 kB
> Active: 31184 kB
> Inactive: 271508 kB
> SwapTotal: 524280 kB
> SwapFree: 524232 kB
> Dirty: 1284 kB
> Writeback: 0 kB
> AnonPages: 22044 kB
> Mapped: 8652 kB
> Slab: 21508 kB
> SReclaimable: 4212 kB
> SUnreclaim: 17296 kB
> PageTables: 3036 kB
> NFS_Unstable: 0 kB
> Bounce: 0 kB
> WritebackTmp: 0 kB
> CommitLimit: 778308 kB
> Committed_AS: 80544 kB
> VmallocTotal: 34359738367 kB
> VmallocUsed: 1740 kB
> VmallocChunk: 34359736619 kB
> HugePages_Total: 0
> HugePages_Free: 0
> HugePages_Rsvd: 0
> HugePages_Surp: 0
> Hugepagesize: 2048 kB
> DirectMap4k: 8128 kB
> DirectMap2M: 516096 kB
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-03-11 7:15 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12832-27@http.bugzilla.kernel.org/>
2009-03-07 20:24 ` Andrew Morton
2009-03-07 21:00 ` Pierre Ossman
2009-03-07 22:13 ` Andrew Morton
2009-03-07 22:53 ` Pierre Ossman
2009-03-08 10:00 ` Pierre Ossman
2009-03-08 10:36 ` Pierre Ossman
2009-03-08 12:38 ` Wu Fengguang
2009-03-08 14:26 ` Pierre Ossman
2009-03-08 15:54 ` Pierre Ossman
2009-03-08 19:11 ` Andrew Morton
2009-03-08 19:23 ` Pierre Ossman
2009-03-07 22:16 ` Andrew Morton
2009-03-09 1:37 ` Wu Fengguang
[not found] ` <20090309020701.GA381@localhost>
2009-03-09 7:40 ` Pierre Ossman
2009-03-09 14:22 ` Wu Fengguang
2009-03-09 15:02 ` Pierre Ossman
2009-03-10 2:41 ` Wu Fengguang
2009-03-10 6:56 ` Pierre Ossman
2009-03-10 8:19 ` Wu Fengguang
2009-03-10 9:55 ` Pierre Ossman
2009-03-10 12:22 ` Wu Fengguang
2009-03-10 13:11 ` Wu Fengguang
2009-03-10 15:52 ` Pierre Ossman
2009-03-10 20:21 ` Pierre Ossman
2009-03-11 1:37 ` Wu Fengguang
[not found] ` <20090311075703.35de2488@mjolnir.ossman.eu>
2009-03-11 7:14 ` Wu Fengguang [this message]
2009-03-11 7:26 ` Pierre Ossman
2009-03-11 7:36 ` Wu Fengguang
2009-03-11 7:57 ` Pierre Ossman
2009-03-11 8:20 ` Wu Fengguang
2009-03-11 13:05 ` Pierre Ossman
2009-03-11 13:00 ` Wu Fengguang
2009-03-11 15:02 ` Pierre Ossman
2009-03-11 15:47 ` Steven Rostedt
2009-03-11 16:46 ` Pierre Ossman
2009-03-11 21:43 ` Pierre Ossman
2009-03-12 6:50 ` Pierre Ossman
2009-03-12 1:08 ` Wu Fengguang
2009-03-12 6:55 ` Pierre Ossman
2009-03-12 7:29 ` Wu Fengguang
2009-03-11 14:25 ` Steven Rostedt
2009-03-11 14:35 ` Pierre Ossman
2009-03-11 16:55 ` Pierre Ossman
2009-03-11 17:28 ` Steven Rostedt
2009-03-11 18:33 ` Pierre Ossman
2009-03-11 18:48 ` Steven Rostedt
2009-03-11 18:56 ` Pierre Ossman
2009-03-11 19:03 ` Steven Rostedt
2009-03-12 2:46 ` KOSAKI Motohiro
2009-03-12 6:53 ` Pierre Ossman
2009-03-10 19:58 ` Pierre Ossman
2009-03-11 0:19 ` KOSAKI Motohiro
2009-03-11 7:22 ` Pierre Ossman
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=20090311071445.GA13584@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=drzeus@drzeus.cx \
--cc=linux-mm@kvack.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