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: <20071026142810.GA14814@redhat.com> Date: Fri, 26 Oct 2007 10:28:10 -0400 From: "Frank Ch. Eigler" <fche@...hat.com> To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> Cc: Roland McGrath <roland@...hat.com>, "Frank Ch. Eigler" <fche@...hat.com>, Denys Vlasenko <vda.linux@...glemail.com>, systemtap@...rces.redhat.com, Christoph Hellwig <hch@...radead.org>, Rusty Russell <rusty@...tcorp.com.au>, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [patch 1/4] Linux Kernel Markers - Architecture Independent Code Hi - On Thu, Oct 25, 2007 at 03:17:22PM -0400, Mathieu Desnoyers wrote: > [...] > Since gcc is required to build the systemtap probes on the development > marchine, I don't see why it would be much harder to also require prople > to install drawf ? Or maybe the "crash" tool ? The crash tool requires the dwarf data to work. The dwarf data for an entire kernel (including all the modules) is on the order of hundreds of megabytes. The symbol & marker list would be one thousandth the size. You can see the deployment attractiveness of the latter. > I guess you must already need to extract the symbols for your kprobes. > Do you use kallsyms for this? Nope. /proc/kallsyms is a another run-time-only source of data, and so is not applicable for off-line (ahead-of-time) mapping. > I would rather prefer not to implement superfluous built-time data > extraction in the kernel build system just to make userspace > simpler. [...] It is not superfluous, as it would solve a real distribution problem. - FChE - 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