linux-kernel - Re: kmemleak suggestion (long message)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1246004270.27533.16.camel@penberg-laptop>
Date:	Fri, 26 Jun 2009 11:17:50 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Sergey Senozhatsky <sergey.senozhatsky@...l.by>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Catalin Marinas <catalin.marinas@....com>,
	"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)

Hi Sergey,

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.

On Fri, 2009-06-26 at 11:14 +0300, Sergey Senozhatsky wrote:
> What do you about suggested ability to filter/block "unwanted" reports?
> IMHO it makes sense.

Well, the thing is, I am not sure it's needed if we implement Ingo's
suggestion. After all, syslog is no longer spammed very hard and you can
do all the filtering in userspace when you read /debug/mm/kmemleak file,
no?

			Pekka

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