This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: s390/s390-64 missing xattr exports
- From: Roland McGrath <roland at frob dot com>
- To: Andreas Jaeger <aj at suse dot de>
- Cc: libc-alpha at sources dot redhat dot com
- Date: Fri, 16 Aug 2002 03:05:58 -0400 (EDT)
- Subject: Re: s390/s390-64 missing xattr exports
If these new *xattr interfaces are taking hold, then perhaps we should
declare them a generic part of the libc interface. In that case, we get an
ENOSYS stub for each call in sysdeps/generic, the symbols can go someplace
generic like misc/Versions, and the syscalls can be listed just once in the
sysdeps/unix/sysv/linux/syscalls.list file (again). Platforms that don't
define the syscall numbers will get the stub versions.
On platforms that provide the syscall numbers but haven't actually
implemented the calls, does that mean they would get SIGSYS or something
nasty like that, or just return ENOSYS, in the kernels preceding the ones
where the calls actually get implemented?