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: Tue, 29 Apr 2008 12:09:51 -0700 (PDT) From: Christoph Lameter <clameter@....com> To: Arjan van de Ven <arjan@...radead.org> cc: Ingo Molnar <mingo@...e.hu>, akpm@...ux-foundation.org, linux-mm@...ck.org, linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...ux-foundation.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl> Subject: Re: [2/2] vmallocinfo: Add caller information On Mon, 28 Apr 2008, Arjan van de Ven wrote: > > Hmmm... Why do we have CONFIG_FRAMEPOINTER then? > > to make the backtraces more accurate. Well so we display out of whack backtraces? There are also issues on platforms that do not have a stack in the classic sense (rotating register file on IA64 and Sparc64 f.e.). Determining a backtrace can be very expensive. > > The current implementation of vmalloc_caller() follows what we have > > done with kmalloc_track_caller. Its low overhead and always on. > > stacktraces aren't entirely free, the cost is O(nr of modules) unfortunately ;( The current implementation /proc/vmallocinfo avoids these issues and with just one caller address it can print one line per vmalloc request. -- 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