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>,
Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [Bug 12832] New: kernel leaks a lot of memory
Date: Wed, 11 Mar 2009 15:36:19 +0800 [thread overview]
Message-ID: <20090311073619.GA26691@localhost> (raw)
In-Reply-To: <20090311082658.06ff605a@mjolnir.ossman.eu>
(add cc)
On Wed, Mar 11, 2009 at 09:26:58AM +0200, Pierre Ossman wrote:
> On Wed, 11 Mar 2009 15:14:45 +0800
> Wu Fengguang <fengguang.wu@intel.com> wrote:
>
> > 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...
> >
>
> Another breakthrough. I turned off everything in kernel/trace, and now
> the missing memory is back. Here's the relevant diff against the
> original .config:
>
> @@ -3677,18 +3639,15 @@
> # CONFIG_BACKTRACE_SELF_TEST is not set
> # CONFIG_LKDTM is not set
> # CONFIG_FAULT_INJECTION is not set
> -CONFIG_LATENCYTOP=y
> +# CONFIG_LATENCYTOP is not set
> # CONFIG_SYSCTL_SYSCALL_CHECK is not set
> CONFIG_HAVE_FTRACE=y
> CONFIG_HAVE_DYNAMIC_FTRACE=y
> -CONFIG_TRACER_MAX_TRACE=y
> -CONFIG_TRACING=y
> # CONFIG_FTRACE is not set
> -CONFIG_IRQSOFF_TRACER=y
> -CONFIG_SYSPROF_TRACER=y
> -CONFIG_SCHED_TRACER=y
> -CONFIG_CONTEXT_SWITCH_TRACER=y
> -# CONFIG_FTRACE_STARTUP_TEST is not set
> +# CONFIG_IRQSOFF_TRACER is not set
> +# CONFIG_SYSPROF_TRACER is not set
> +# CONFIG_SCHED_TRACER is not set
> +# CONFIG_CONTEXT_SWITCH_TRACER is not set
>
> I'll enable them one at a time and see when the bug reappears, but if
> you have some ideas on which it could be, that would be helpful. The
> machine takes some time to recompile a kernel. :)
A quick question: are there any possibility of ftrace memory reservation?
Thanks,
Fengguang
--
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:37 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
2009-03-11 7:26 ` Pierre Ossman
2009-03-11 7:36 ` Wu Fengguang [this message]
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=20090311073619.GA26691@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 \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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