| 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
| ||
|
Message-ID: <20110610190956.GA2742@maxin> Date: Fri, 10 Jun 2011 22:09:56 +0300 From: Maxin B John <maxin.john@...il.com> To: rdunlap@...otime.net Cc: catalin.marinas@....com, dbaluta@...acom.com, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] Documentation: update kmemleak architecture support info >> I think Daniel's suggestion is better, we don't have to worry about >> changing the documentation every time we add a new architecture. I agree with that. > Please send an updated patch without the currently-supported list > of architectures. Please find the updated patch below: Signed-off-by: Maxin B. John <maxin.john@...il.com> --- diff --git a/Documentation/kmemleak.txt b/Documentation/kmemleak.txt index 090e6ee..51063e6 100644 --- a/Documentation/kmemleak.txt +++ b/Documentation/kmemleak.txt @@ -11,7 +11,9 @@ with the difference that the orphan objects are not freed but only reported via /sys/kernel/debug/kmemleak. A similar method is used by the Valgrind tool (memcheck --leak-check) to detect the memory leaks in user-space applications. -Kmemleak is supported on x86, arm, powerpc, sparc, sh, microblaze and tile. + +Please check DEBUG_KMEMLEAK dependencies in lib/Kconfig.debug for supported +architectures. Usage ----- -- 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/
Powered by blists - more mailing lists