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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 16 Jun 2014 10:58:37 -0400
From:	Rich Felker <>
To:	Andi Kleen <>
Cc:	Ian Lance Taylor <>,
	Andy Lutomirski <>,
	"H. Peter Anvin" <>,
	Mikael Pettersson <>,
	Russ Cox <>,
	Linux API <>,
	"" <>,
	X86 ML <>
Subject: Re: [RFC 0/2] __vdso_findsym

On Mon, Jun 16, 2014 at 04:38:01PM +0200, Andi Kleen 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?
> The proposal is 10+ years too late.

I addressed that in one of my first emails to this thread. I don't
think adding it now is immediately useful, but it will be very nice to
have in a few years when optimizing for kernels from 2014 and earlier
is no longer a priority. I would expect new users of vdso at that time
not to bother with the ELF parsing ugliness and simply to use the
lookup interface. It's not like they'd be losing any functionality on
old kernels, just some performance due to falling back to the syscall.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists