linux-kernel - kmemleak issue on ARM target

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

Message-ID: <9bde694e1003040113k3b573957h1b831c8d25205d22@mail.gmail.com>
Date:	Thu, 4 Mar 2010 14:43:10 +0530
From:	naveen yadav <yad.naveen@...il.com>
To:	catalin.marinas@....com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: kmemleak issue on ARM target

Hi Catalin Marinas ,

W am facing one issue on ARM target, we have 512 MB ram on our target,
we port your patch of
kmemleak(http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-04/msg11830.html)

We are facing problem in DEBUG_KMEMLEAK_EARLY_LOG_SIZE we cannot
increase its size above 1000 because of our kernel Image size for
embedded board
has some limit that if it increase we cannot execute it. so is there
any implementaion possible using vmalloc and not statically allocating
the log of array or else any suggestion.

kind regards
Naveen
--
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/