This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: support for calling Linux syscalls directly
- From: chrubis at suse dot cz
- To: David Miller <davem at davemloft dot net>
- Cc: hpa at zytor dot com, vapier at gentoo dot org, libc-alpha at sourceware dot org,keescook at chromium dot org
- Date: Tue, 12 Feb 2013 19:03:20 +0100
- Subject: Re: support for calling Linux syscalls directly
- References: <201301242314.47793.vapier@gentoo.org><5109A662.7050101@zytor.com><20130212174638.GB25044@rei><20130212.125252.1057529665632731599.davem@davemloft.net>
Hi!
> > I do the LTP[1] which makes legitimate use of syscall(3) as for the
> > testing purposes we need to be able to call bare syscalls in order to
> > validate both glibc and kernel API. And removing the call would mess
> > backward compatibility.
>
> I don't think it makes sense for every source tree that wants to
> call syscall directly to have to duplicate over and over again the
> argument passing quirks of various architectures.
>
> Multiple instances of such tricky code means multiple places for
> the same bugs over and over again.
I'm all for deduplication. And having an up to date table of linux
syscalls numbers would greatly help us too (that way we could get rid of
the one in LTP). But the only usable way I can think of is to create a
git submodule which could be easily included in other repos as any
library you make wouldn't be included in current distros and wouldn't
make it into enterprise distros in less than five years.
--
Cyril Hrubis
chrubis@suse.cz