Re: kmemleak suggestion (long message)

[Sergey Senozhatsky]

On (06/26/09 08:59), Ingo Molnar wrote:
> Date: Fri, 26 Jun 2009 08:59:23 +0200
> From: Ingo Molnar <mingo@xxxxxxx>
> To: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxx>
> Cc: Catalin Marinas <catalin.marinas@xxxxxxx>,
> 	Pekka Enberg <penberg@xxxxxxxxxxxxxx>,
> 	"Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>,
> 	Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>,
> 	linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx
> Subject: Re: kmemleak suggestion (long message)
> User-Agent: Mutt/1.5.18 (2008-05-17)
> 
> 
> * Sergey Senozhatsky <sergey.senozhatsky@xxxxxxx> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/