This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Fix Arm __ASSUME_COPY_FILE_RANGE (bug 23915) [committed]
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: <libc-alpha at sourceware dot org>
- Date: Wed, 9 Jan 2019 17:58:34 +0000
- Subject: Re: Fix Arm __ASSUME_COPY_FILE_RANGE (bug 23915) [committed]
- References: <alpine.DEB.2.21.1811231754100.6394@digraph.polyomino.org.uk> <87bm6cou8a.fsf@oldenburg.str.redhat.com> <alpine.DEB.2.21.1811261640170.24694@digraph.polyomino.org.uk> <87sgy2t2ar.fsf@oldenburg2.str.redhat.com>
On Wed, 9 Jan 2019, Florian Weimer wrote:
> > My approach is to examine the diffs for the kernel version that introduced
> > the syscall, and check whether it's present (asm/unistd.h, and syscall
> > table, and any relevant compat syscall table) for each (architecture, ABI)
> > pair supported by glibc not using the asm-generic syscall ABI.
>
> Can we put a list somewhere of the files that need checking, for the
> supported glibc architectures?
It tends to change with the Linux kernel version, as architectures change
how they handle their syscall tables. (Hopefully ongoing changes to unify
the machinery more between different architectures will make such checks
easier for future kernel versions - while not helping when it's past
syscalls you're looking at.)
--
Joseph S. Myers
joseph@codesourcery.com