linux-kernel - Re: [PATCH] kmemleak: config-options: Default buffer size for kmemleak

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: <20100622113135.GB20140@linux-sh.org>
Date:	Tue, 22 Jun 2010 20:31:36 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Sankar P <sankar.curiosity@...il.com>
Cc:	penberg@...helsinki.fi, linux-sh@...r.kernel.org,
	linux-kernel@...r.kernel.org, lrodriguez@...eros.com,
	catalin.marinas@....com, rnagarajan@...ell.com, teheo@...ell.com,
	linux-mm@...ck.org, paulmck@...ux.vnet.ibm.com, mingo@...e.hu,
	akpm@...ux-foundation.org
Subject: Re: [PATCH] kmemleak: config-options: Default buffer size for kmemleak

On Tue, Jun 22, 2010 at 02:16:43PM +0530, Sankar P wrote:
> If we try to find the memory leaks in kernel that is
> compiled with 'make defconfig', the default buffer size
> of DEBUG_KMEMLEAK_EARLY_LOG_SIZE seem to be inadequate.
> 
> Change the buffer size from 400 to 1000,
> which is sufficient for most cases.
> 
Or you could just bump it up in your config where you seem to be hitting
this problem. The default of 400 is sufficient for most people, so
bloating it up for a corner case seems a bit premature. Perhaps
eventually we'll have no choice and have to tolerate the bloat, as we did
with LOG_BUF_SHIFT, but it's not obvious that we've hit that point with
kmemleak yet.
--
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/