[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090626074847.GA3451@localdomain.by>
Date: Fri, 26 Jun 2009 10:48:48 +0300
From: Sergey Senozhatsky <sergey.senozhatsky@...l.by>
To: Ingo Molnar <mingo@...e.hu>
Cc: Catalin Marinas <catalin.marinas@....com>,
Pekka Enberg <penberg@...helsinki.fi>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: kmemleak suggestion (long message)
On (06/26/09 08:59), Ingo Molnar wrote:
> Date: Fri, 26 Jun 2009 08:59:23 +0200
> From: Ingo Molnar <mingo@...e.hu>
> To: Sergey Senozhatsky <sergey.senozhatsky@...l.by>
> Cc: Catalin Marinas <catalin.marinas@....com>,
> Pekka Enberg <penberg@...helsinki.fi>,
> "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
> Andrew Morton <akpm@...ux-foundation.org>,
> linux-kernel@...r.kernel.org, linux-mm@...ck.org
> Subject: Re: kmemleak suggestion (long message)
> User-Agent: Mutt/1.5.18 (2008-05-17)
>
>
> * Sergey Senozhatsky <sergey.senozhatsky@...l.by> wrote:
>
> > Hello.
> >
> > Currently kmemleak prints info about all objects. I guess
> > sometimes kmemleak gives you more than you actually need.
>
> It prints _a lot_ of info and spams the syslog. I lost crash info a
> few days ago due to that: by the time i inspected a crashed machine
> the tons of kmemleak output scrolled out the crash from the dmesg
> buffer.
>
> This is not acceptable.
>
Agreed.
> Instead it should perhaps print _at most_ a single line every few
> minutes, printing a summary about _how many_ leaked entries it
> suspects, and should offer a /debug/mm/kmemleak style of file where
> the entries can be read out from.
>
> Ok?
>
> Ingo
>
Agreed.
Sergey
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists