From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail203.messagelabs.com (mail203.messagelabs.com [216.82.254.243]) by kanga.kvack.org (Postfix) with ESMTP id B8A3A6B004D for ; Fri, 26 Jun 2009 02:57:46 -0400 (EDT) Date: Fri, 26 Jun 2009 08:59:23 +0200 From: Ingo Molnar 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> Sender: owner-linux-mm@kvack.org To: Sergey Senozhatsky Cc: Catalin Marinas , Pekka Enberg , "Paul E. McKenney" , Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: * Sergey Senozhatsky 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, 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: email@kvack.org