Date: Fri, 26 Jun 2009 08:59:23 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Sergey Senozhatsky <sergey.senozhatsky@mail.by>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
       Pekka Enberg <penberg@cs.helsinki.fi>,
       "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
       Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org,
       linux-mm@kvack.org
Subject: Re: kmemleak suggestion (long message)
Message-ID: <20090626065923.GA14078@elte.hu>
References: <20090625221816.GA3480@localdomain.by>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090625221816.GA3480@localdomain.by>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 923
Lines: 28


* Sergey Senozhatsky <sergey.senozhatsky@mail.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.

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/