linux-kernel - Re: [PATCH 2/2] Documentation: Add CONFIG_DEBUG_KMEMLEAK_DEFAULT

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] [day] [month] [year] [list]

Message-ID: <544AA421.6040705@infradead.org>
Date:	Fri, 24 Oct 2014 12:10:25 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Masanari Iida <standby24x7@...il.com>, catalin.marinas@....com,
	corbet@....net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] Documentation: Add CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF
 case

On 10/24/14 05:25, Masanari Iida wrote:
> This patch add a case with CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF=y.
> 
> Signed-off-by: Masanari Iida <standby24x7@...il.com>
> ---
>  Documentation/kmemleak.txt | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/kmemleak.txt b/Documentation/kmemleak.txt
> index f4f033c..0f2bbd8 100644
> --- a/Documentation/kmemleak.txt
> +++ b/Documentation/kmemleak.txt
> @@ -62,6 +62,10 @@ Memory may be allocated or freed before kmemleak is initialised and
>  these actions are stored in an early log buffer. The size of this buffer
>  is configured via the CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE option.
>  
> +If CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF are enabled, the kmemleak is

                                        is enabled, kmemleak is

> +disabled by default. Passing "kmemleak=on" on the kernel command
> +line enables the function. 
> +
>  Basic Algorithm
>  ---------------
>  
> 


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