This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Principles for syscall wrappers, again
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Andreas Schwab <schwab at linux-m68k dot org>, Roland McGrath <roland at hack dot frob dot com>
- Cc: Joseph Myers <joseph at codesourcery dot com>, libc-alpha at sourceware dot org
- Date: Sat, 23 May 2015 23:43:18 -0400
- Subject: Re: Principles for syscall wrappers, again
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 10 dot 1505182114090 dot 16300 at digraph dot polyomino dot org dot uk> <20150522235242 dot 50BF82C3ABD at topped-with-meat dot com> <m27frzd7sq dot fsf at linux-m68k dot org>
On 05/23/2015 04:20 AM, Andreas Schwab wrote:
> Roland McGrath <roland@hack.frob.com> writes:
>
>> We could provide OS-specific ABIs in an OS-specific shared library,
>> e.g. libinux-syscalls.so.N.
>
> Wouldn't it be small enough to make it static-only? I think the
> OS-specific syscalls are unlikely be used in many places.
What about the security implications of this? Say if we find a bug
in the argument handling on the glibc side? Or cancellation on the
glibc side?
For the record I like Roland's propose of a libinux-syscalls.so.N,
but would want it to be AS_NEEDED, since to be useful it must be
transparent to the average GNU/Linux user.
Cheers,
Carlos.