public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Fix Arm __ASSUME_COPY_FILE_RANGE (bug 23915) [committed]
Date: Wed, 09 Jan 2019 17:58:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.21.1901091756550.22775@digraph.polyomino.org.uk> (raw)
In-Reply-To: <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

      reply	other threads:[~2019-01-09 17:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 17:54 Joseph Myers
2018-11-26 13:15 ` Florian Weimer
2018-11-26 16:46   ` Joseph Myers
2018-11-26 18:14     ` Adhemerval Zanella
2018-11-27 14:33       ` Arnd Bergmann
2019-01-09 12:59     ` Florian Weimer
2019-01-09 17:58       ` Joseph Myers [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1901091756550.22775@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).