From: Mikael Pettersson <mikpelinux@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Russ Cox <rsc@golang.org>,
linux-api@vger.kernel.org, Ian Taylor <iant@golang.org>,
linux-kernel@vger.kernel.org, X86 ML <x86@kernel.org>,
dalias@libc.org
Subject: Re: [RFC 0/2] __vdso_findsym
Date: Sun, 15 Jun 2014 16:25:37 +0200 [thread overview]
Message-ID: <21405.44257.742122.786960@gargle.gargle.HOWL> (raw)
In-Reply-To: <cover.1402769596.git.luto@amacapital.net>
Andy Lutomirski writes:
> The idea is to add AT_VDSO_FINDSYM pointing at __vdso_findsym. This
> implements __vdso_findsym.
>
> This would make it easier for runtimes that don't otherwise implement
> ELF loaders to use the vdso.
>
> Thoughts?
I'm opposed to this based on the principle that the kernel should NOT
be a dumping ground for random code that user-space can and should
implement for itself. As long as the vdso is correctly formatted ELF,
then parsing it is easy, and the kernel should not care at all if or
how user-space accesses it.
The fact that golang got it wrong is not an argument for moving this
functionality into the kernel.
/Mikael
next prev parent reply other threads:[~2014-06-15 14:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 18:16 Andy Lutomirski
2014-06-14 18:16 ` [RFC 1/2] uapi: Add some missing dynamic table-related definitions to elf.h Andy Lutomirski
2014-06-14 18:16 ` [RFC 2/2] [NOT READY] x86/vdso: Add __vdso_findsym Andy Lutomirski
2014-06-14 21:30 ` [RFC 0/2] __vdso_findsym Rich Felker
2014-06-14 22:38 ` Andy Lutomirski
2014-06-14 23:36 ` H. Peter Anvin
2014-06-15 3:59 ` H. Peter Anvin
2014-06-15 6:49 ` Andy Lutomirski
2014-06-15 14:25 ` Mikael Pettersson [this message]
2014-06-15 14:35 ` Rich Felker
2014-06-15 15:47 ` Andy Lutomirski
2014-06-15 17:05 ` H. Peter Anvin
2014-06-15 17:40 ` Andy Lutomirski
2014-06-15 17:57 ` H. Peter Anvin
2014-06-15 18:20 ` Andy Lutomirski
2014-06-15 18:39 ` H. Peter Anvin
2014-06-15 18:54 ` Andy Lutomirski
2014-06-15 19:14 ` H. Peter Anvin
2014-06-15 19:22 ` Ian Lance Taylor
2014-06-15 19:31 ` H. Peter Anvin
2014-06-15 19:50 ` Ian Lance Taylor
2014-06-15 19:56 ` H. Peter Anvin
2014-06-15 20:53 ` Andy Lutomirski
2014-06-15 21:13 ` H. Peter Anvin
2014-06-16 0:55 ` Rich Felker
2014-06-16 2:36 ` Andi Kleen
2014-06-16 3:49 ` Rich Felker
2014-06-16 14:08 ` Ian Lance Taylor
2014-06-16 14:38 ` Andi Kleen
2014-06-16 14:58 ` Rich Felker
2014-06-16 15:31 ` Ian Lance Taylor
2014-06-16 15:42 ` Rich Felker
2014-06-20 15:55 ` Andy Lutomirski
2014-06-20 16:07 ` Rich Felker
2014-06-16 14:56 ` Rich Felker
2014-06-15 18:20 ` H. Peter Anvin
2014-06-15 18:22 ` Andy Lutomirski
2014-06-16 6:39 ` Rich Felker
2014-06-16 1:06 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21405.44257.742122.786960@gargle.gargle.HOWL \
--to=mikpelinux@gmail.com \
--cc=dalias@libc.org \
--cc=iant@golang.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=rsc@golang.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®