Date: Fri, 26 Jun 2009 11:14:52 +0300
From: Sergey Senozhatsky <sergey.senozhatsky@mail.by>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Ingo Molnar <mingo@elte.hu>, Catalin Marinas <catalin.marinas@arm.com>,
       "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: <20090626081452.GB3451@localdomain.by>
References: <20090625221816.GA3480@localdomain.by>
 <20090626065923.GA14078@elte.hu>
 <84144f020906260007u3e79086bv91900e487ba0fb50@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <84144f020906260007u3e79086bv91900e487ba0fb50@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 763
Lines: 23

On (06/26/09 10:07), Pekka Enberg wrote:
> > 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.
> 
> Yup, makes tons of sense.
> 
>                                      Pekka
> 

Hello Pekka,
What do you about suggested ability to filter/block "unwanted" reports?
IMHO it makes sense.

	Sergey
--
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/