From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
Minchan Kim <minchan.kim@gmail.com>,
Rik van Riel <riel@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: tracking memory usage/leak in "inactive" field in /proc/meminfo?
Date: Fri, 12 Feb 2010 17:04:06 +0900 (JST) [thread overview]
Message-ID: <20100212170248.73B8.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <4B7504D2.1040903@nortel.com>
> backtrace:
> [<ffffffff8061c162>] kmemleak_alloc_page+0x1eb/0x380
> [<ffffffff80276ae8>] __pagevec_lru_add_active+0xb6/0x104
> [<ffffffff80276b85>] lru_cache_add_active+0x4f/0x53
> [<ffffffff8027d182>] do_wp_page+0x355/0x6f6
> [<ffffffff8027eef1>] handle_mm_fault+0x62b/0x77c
> [<ffffffff80632557>] do_page_fault+0x3c7/0xba0
> [<ffffffff8062fb79>] error_exit+0x0/0x51
> [<ffffffffffffffff>] 0xffffffffffffffff
>
> and
>
> backtrace:
> [<ffffffff8061c162>] kmemleak_alloc_page+0x1eb/0x380
> [<ffffffff80276ae8>] __pagevec_lru_add_active+0xb6/0x104
> [<ffffffff80276b85>] lru_cache_add_active+0x4f/0x53
> [<ffffffff8027eddc>] handle_mm_fault+0x516/0x77c
> [<ffffffff8027f180>] get_user_pages+0x13e/0x462
> [<ffffffff802a2f65>] get_arg_page+0x6a/0xca
> [<ffffffff802a30bf>] copy_strings+0xfa/0x1d4
> [<ffffffff802a31c7>] copy_strings_kernel+0x2e/0x43
> [<ffffffff802d33fb>] compat_do_execve+0x1fa/0x2fd
> [<ffffffff8021e405>] sys32_execve+0x44/0x62
> [<ffffffff8021def5>] ia32_ptregs_common+0x25/0x50
> [<ffffffffffffffff>] 0xffffffffffffffff
>
> I'll dig into them further, but do either of these look like known issues?
no known issue.
AFAIK, 2.6.27 - 2.6.33 don't have such problem.
next prev parent reply other threads:[~2010-02-12 8:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 16:51 Chris Friesen
2010-02-10 0:32 ` KOSAKI Motohiro
2010-02-10 3:50 ` Balbir Singh
2010-02-10 4:09 ` KOSAKI Motohiro
2010-02-10 17:05 ` Chris Friesen
2010-02-11 0:45 ` Minchan Kim
2010-02-11 18:54 ` Chris Friesen
2010-02-11 19:04 ` Rik van Riel
2010-02-12 2:38 ` Minchan Kim
2010-02-12 7:35 ` Chris Friesen
2010-02-12 8:04 ` KOSAKI Motohiro [this message]
2010-02-15 15:50 ` Chris Friesen
2010-02-15 17:00 ` Rik van Riel
2010-02-16 16:52 ` Chris Friesen
2010-02-16 17:12 ` Rik van Riel
2010-02-16 21:26 ` Chris Friesen
2010-02-16 22:22 ` Rik van Riel
2010-02-18 15:39 ` tracking memory usage/leak in "inactive" field in /proc/meminfo? -- solved Chris Friesen
2010-02-12 17:50 ` tracking memory usage/leak in "inactive" field in /proc/meminfo? Catalin Marinas
2010-02-13 6:29 ` Balbir Singh
2010-02-15 16:02 ` Chris Friesen
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=20100212170248.73B8.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.com \
/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
all inboxes | Powered by JetHome®