linux-kernel - Re: [PATCH 12/15] kmemleak: Enable the building of the memory leak detector

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: <1228936817.9737.102.camel@nimitz>
Date:	Wed, 10 Dec 2008 11:20:17 -0800
From:	Dave Hansen <dave@...ux.vnet.ibm.com>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 12/15] kmemleak: Enable the building of the memory leak
	detector

On Wed, 2008-12-10 at 18:28 +0000, Catalin Marinas wrote:
> +config DEBUG_MEMLEAK
> +       bool "Kernel memory leak detector"
> +       default n
> +       depends on EXPERIMENTAL
> +       select DEBUG_SLAB if SLAB
> +       select SLUB_DEBUG if SLUB
> +       select DEBUG_FS
> +       select STACKTRACE
> +       select FRAME_POINTER
> +       select KALLSYMS

So, not all architectures have STACKTRACE or FRAME_POINTER.  I think a
few of these should at least be done with depends.

Is this feature accessible if DEBUG_FS=n?  It seems to compile OK, but I
wonder if it is useful.

-- Dave

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