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: <1277210104.29532.13.camel@e102109-lin.cambridge.arm.com>
Date:	Tue, 22 Jun 2010 13:35:04 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	Paul Mundt <lethal@...ux-sh.org>,
	Sankar P <sankar.curiosity@...il.com>,
	linux-sh@...r.kernel.org, linux-kernel@...r.kernel.org,
	lrodriguez@...eros.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, 2010-06-22 at 13:21 +0100, Pekka Enberg wrote:
> On Tue, Jun 22, 2010 at 3:05 PM, Catalin Marinas
> <catalin.marinas@....com> wrote:
> > The defconfig change for this specific platform may be a better option
> > but I thought defconfigs are to provide a stable (and maybe close to
> > optimal) configuration without all the debugging features enabled
> > (especially those slowing things down considerably).
> 
> The defconfig change was definitely not a clean solution to this
> problem. Better bake the fix in Kconfig proper even if it means
> dependency on CONFIG_SH or something.

OK, maybe something like this

	default 1000 if SH
	default 400

It seems that kbuild only considers the first encounter of "default".

Thanks.

-- 
Catalin

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