| 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: Mon, 28 Apr 2008 12:48:49 -0700 From: Arjan van de Ven <arjan@...radead.org> To: Christoph Lameter <clameter@....com> 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 Tue, 29 Apr 2008 10:08:29 -0700 (PDT) Christoph Lameter <clameter@....com> wrote: > On Tue, 29 Apr 2008, Ingo Molnar wrote: > > > i pointed out how it should be done _much cleaner_ (and much > > smaller - only a single patch needed) via stack-trace, without > > changing a dozen architectures, and even gave a patch to make it > > all easier for you: > > > > http://lkml.org/lkml/2008/3/19/568 > > http://lkml.org/lkml/2008/3/21/88 > > > > in fact, a stacktrace printout is much more informative as well to > > users, than a punny __builtin_return_address(0)! > > Sorry lost track of this issue. Adding stracktrace support is not a > trivial thing and will change the basic handling of vmallocinfo. > > Not sure if stacktrace support can be enabled without a penalty on > various platforms. Doesnt this require stackframes to be formatted in > a certain way? it doesn't. -- 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