| 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: <CAKOQZ8zk8KfkObSZg8fmhZXm9nXQSneOywvV-NBj=N-tNWjNPg@mail.gmail.com> Date: Mon, 16 Jun 2014 08:31:39 -0700 From: Ian Lance Taylor <iant@...ang.org> To: Andi Kleen <andi@...stfloor.org> Cc: Andy Lutomirski <luto@...capital.net>, "H. Peter Anvin" <hpa@...or.com>, Rich Felker <dalias@...c.org>, Mikael Pettersson <mikpelinux@...il.com>, Russ Cox <rsc@...ang.org>, Linux API <linux-api@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, X86 ML <x86@...nel.org> Subject: Re: [RFC 0/2] __vdso_findsym On Mon, Jun 16, 2014 at 7:38 AM, Andi Kleen <andi@...stfloor.org> wrote: >> I think this issue started when some of the Go developers questioned >> why the kernel needed to provide a very complex interface--parsing an >> ELF shared shared library--for very simple functionality--looking up >> the address of a magic function. This approach has required special >> support not just in Go, but also in the dynamic linker and gdb, and >> does not work well for statically linked binaries. The support in gdb >> is perhaps a good idea, but elsewhere it does not make sense. >> >> So why not provide a simple interface? > > What good would it do now that everyone already supports it? Do statically linked binaries use the vDSO calls? Ian -- 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