unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	 Joseph Myers <joseph@codesourcery.com>,
	 Paul Eggert <eggert@cs.ucla.edu>,
	 Andreas Schwab <schwab@suse.de>,
	 Alistair Francis <alistair23@gmail.com>,
	 Alistair Francis <alistair.francis@wdc.com>,
	 GNU C Library <libc-alpha@sourceware.org>,
	 Siddhesh Poyarekar <siddhesh@gotplt.org>,
	 Florian Weimer <fw@deneb.enyo.de>,
	 Zack Weinberg <zackw@panix.com>,
	 Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH v4 1/2] y2038: linux: Provide __timerfd_gettime64 implementation
Date: Tue, 07 Jan 2020 13:49:46 +0100	[thread overview]
Message-ID: <87ftgrtor9.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20200107102752.396f7f6f@jawa> (Lukasz Majewski's message of "Tue, 7 Jan 2020 10:27:52 +0100")

* Lukasz Majewski:

> Only Linux version >= 5.1 supports 64 bit time on archs with __WORDSIZE
> = 32. I do guess (but I may be wrong here) that the arch-syscall is
> supposed to reflect the exact syscalls provided by kernel headers used
> for building (to help with validation of Y2038 patches).

The tables are supposed to be complete in the sense that they include
all system calls which

(a) have a system call number assigned in some recent kernel version,
    and

(b) are actually used during the glibc build in some way.

The intent is that you can build glibc against older kernel headers (say
Linux 4.18) and still get the exact same system call profile as you
would get when building against Linux 5.3 (or Linux 4.18 with random
system call backports).

As Adhemerval pointed out, (a) can be problematic in the sense that
system call numbers could be added late on some architectures.  This
only matters if their existence actually affects the glibc build, as per
(b).  But if it does, we would have to update the tables.

Thanks,
Florian


      parent reply	other threads:[~2020-01-07 12:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 12:17 [PATCH v4 1/2] y2038: linux: Provide __timerfd_gettime64 implementation Lukasz Majewski
2020-01-06 12:17 ` [PATCH v4 2/2] y2038: linux: Provide __timerfd_settime64 implementation Lukasz Majewski
2020-01-06 21:06   ` Adhemerval Zanella
2020-01-06 20:34 ` [PATCH v4 1/2] y2038: linux: Provide __timerfd_gettime64 implementation Adhemerval Zanella
2020-01-07  9:27   ` Lukasz Majewski
2020-01-07 12:36     ` Adhemerval Zanella
2020-01-07 14:25       ` Lukasz Majewski
2020-01-07 15:26         ` Arnd Bergmann
2020-01-07 20:16         ` Adhemerval Zanella
2020-01-07 20:22           ` Arnd Bergmann
2020-01-07 23:06           ` Lukasz Majewski
2020-01-07 12:49     ` Florian Weimer [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

  List information: https://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=87ftgrtor9.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=carlos@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=fw@deneb.enyo.de \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=lukma@denx.de \
    --cc=schwab@suse.de \
    --cc=siddhesh@gotplt.org \
    --cc=zackw@panix.com \
    /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).