| 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
| ||
|
Date: Fri, 4 May 2012 15:24:59 -0400 From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> To: Yinghai Lu <yinghai@...nel.org> Cc: linux-kernel@...r.kernel.org, tj@...nel.org, hpa@...ux.intel.com, paul.gortmaker@...driver.com, akpm@...ux-foundation.org, linux-mm@...ck.org Subject: Re: [RFC PATCH] Expand memblock=debug to provide a bit more details (v1). On Fri, May 04, 2012 at 12:22:58PM -0700, Yinghai Lu wrote: > On Fri, May 4, 2012 at 11:49 AM, Konrad Rzeszutek Wilk > <konrad.wilk@...cle.com> wrote: > > While trying to track down some memory allocation issues, I realized that > > memblock=debug was giving some information, but for guests with 256GB or > > so the majority of it was just: > > > > memblock_reserve: [0x00003efeeea000-0x00003efeeeb000] __alloc_memory_core_early+0x5c/0x64 > > > > which really didn't tell me that much. With these patches I know it is: > > > > memblock_reserve: [0x00003ffe724000-0x00003ffe725000] (4kB) vmemmap_pmd_populate+0x4b/0xa2 > > > > .. which isn't really that useful for the problem I was tracking down, but > > it does help in figuring out which routines are using memblock. > > > > that RET_IP is not very helpful for debugging. Is there a better way of doing it that is automatic? > > Actually I have local debug patch for memblock. please check if that > is going to help debugging. > > Thanks > > Yinghai -- 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