From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 108069 invoked by alias); 9 Jan 2019 17:58:45 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 108028 invoked by uid 89); 9 Jan 2019 17:58:42 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=ongoing, somewhere X-HELO: relay1.mentorg.com Date: Wed, 09 Jan 2019 17:58:00 -0000 From: Joseph Myers To: Florian Weimer CC: Subject: Re: Fix Arm __ASSUME_COPY_FILE_RANGE (bug 23915) [committed] In-Reply-To: <87sgy2t2ar.fsf@oldenburg2.str.redhat.com> Message-ID: References: <87bm6cou8a.fsf@oldenburg.str.redhat.com> <87sgy2t2ar.fsf@oldenburg2.str.redhat.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2019-01/txt/msg00210.txt.bz2 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