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]

Date:	Fri, 26 Jun 2009 10:42:28 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	Catalin Marinas <catalin.marinas@....com>,
	Sergey Senozhatsky <sergey.senozhatsky@...l.by>,
	"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)


* Pekka Enberg <penberg@...helsinki.fi> wrote:

> On Fri, 2009-06-26 at 09:25 +0100, Catalin Marinas wrote:
>
> > BTW, this was questioned in the past as well - do we still need 
> > the automatic scanning from a kernel thread? Can a user cron job 
> > just read the kmemleak file?
> 
> I think the kernel thread makes sense so that we get an early 
> warning in syslog. Ingo, what's your take on this from autoqa 
> point of view?

it would be nice to have more relevant messages. Many of the 
messages seem false positives, right? So it would be nice to 
constrain kmemleak into a mode of operation that makes its 
backtraces worth looking at. A message about suspected leaks is 
definitely useful, it just shouldnt be printed too frequently.

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