From: Lukasz Majewski <lukma@denx.de>
To: Florian Weimer <fweimer@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Joseph Myers <joseph@codesourcery.com>,
Alistair Francis <alistair.francis@wdc.com>,
GNU C Library <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Palmer Dabbelt <palmer@sifive.com>,
macro@wdc.com, Zong Li <zongbox@gmail.com>,
Zong Li <zong@andestech.com>,
Alistair Francis <alistair23@gmail.com>
Subject: Re: [RFC v2 03/20] y2038: linux: Provide __clock_settime64 implementation
Date: Wed, 26 Jun 2019 22:49:00 -0000 [thread overview]
Message-ID: <20190627004931.79b99cdf@jawa> (raw)
In-Reply-To: <87imssjsa7.fsf@oldenburg2.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1986 bytes --]
Hi Florian,
> * Lukasz Majewski:
>
> > Hi Arnd,
> >
> >> We will probably keep them as an option in the kernel until 2038,
> >> but leave it to the distro or embedded system design to turn them
> >> on or off.
> >
> > Isn't this the ABI break on demand ?
>
> Yes, it is. It happened with vsyscall, too.
>
> Stuff like that is only feasible if you expect that a dynamically
> linked libc is the ultimate ABI boundary for applications. I don't
> think that's realistic or actually intended, especially for things
> like futexes.
>
> > For following setup: WORDSIZE=32, TIMESIZE=32 and kernel with
> > __NR_clock_settime returning -ENOSYS (disabled by embedded system
> > designer in the kernel), but supporting __NR_clock_settime64 (for
> > example 32 bit ARM):
> >
> > The policy question - shall the user space binary after calling
> > clock_settime:
> >
> > 1. Receive -ENOSYS as the __NR_clock_settime was used to fulfill the
> > request
> >
> > or
> >
> > 2. Receive 0 (operation succeed) as the available
> > __NR_clock_settime64 has been used to perform the requested
> > operation.
> >
> >
> > For the proposed patch (clock_settime) - the option 2 is now
> > performed.
>
> In my opinion, an existing 32-bit architecture which does not provide
> the clock_settime system call (that it has provided before) is just
> broken, and will be so at least until 2038.
Am I correct, that you opt for first option that glibc shall return
just -ENOSYS in that case?
>
> We can add the fallback code in glibc, but that will only give people
> the wrong idea that they can disable the 32-bit system calls. It's
> just not true.
>
> Thanks,
> Florian
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-26 22:49 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 0:11 [RFC v2 00/20] RISC-V glibc port for the 32-bit Alistair Francis
2019-06-25 0:11 ` [RFC v2 05/20] sysdeps/nanosleep: Use clock_nanosleep_time64 if avaliable Alistair Francis
2019-06-25 8:24 ` Andreas Schwab
2019-06-25 8:59 ` Arnd Bergmann
2019-06-26 18:23 ` Alistair Francis
2019-06-25 0:11 ` [RFC v2 10/20] Documentation for the RISC-V 32-bit port Alistair Francis
2019-06-25 0:11 ` [RFC v2 03/20] y2038: linux: Provide __clock_settime64 implementation Alistair Francis
2019-06-25 11:05 ` Arnd Bergmann
2019-06-25 15:51 ` Lukasz Majewski
2019-06-25 16:39 ` Arnd Bergmann
2019-06-26 9:07 ` Lukasz Majewski
2019-06-26 12:36 ` Arnd Bergmann
2019-06-26 15:04 ` Lukasz Majewski
2019-06-26 15:11 ` Florian Weimer
2019-06-26 22:49 ` Lukasz Majewski [this message]
2019-06-27 7:15 ` Florian Weimer
2019-06-27 7:37 ` Lukasz Majewski
2019-06-26 18:58 ` Arnd Bergmann
2019-06-26 22:55 ` Lukasz Majewski
2019-06-27 7:46 ` Arnd Bergmann
2019-06-27 10:36 ` Lukasz Majewski
2019-06-27 13:32 ` Arnd Bergmann
2019-06-27 14:08 ` Lukasz Majewski
2019-06-27 14:57 ` Arnd Bergmann
2019-06-27 15:23 ` Lukasz Majewski
2019-06-27 15:46 ` Arnd Bergmann
2019-06-27 16:17 ` Lukasz Majewski
2019-06-27 21:26 ` Arnd Bergmann
2019-06-27 22:08 ` Lukasz Majewski
2019-07-04 0:08 ` Alistair Francis
2019-07-04 8:13 ` Lukasz Majewski
2019-07-08 9:32 ` Lukasz Majewski
2019-06-27 20:11 ` Alistair Francis
2019-06-27 21:02 ` Lukasz Majewski
2019-07-08 10:49 ` Joseph Myers
2019-06-25 0:11 ` [RFC v2 01/20] y2038: Introduce internal for glibc struct __timespec64 Alistair Francis
2019-06-25 0:11 ` [RFC v2 07/20] sysdeps/gettimeofday: Use clock_gettime64 if avaliable Alistair Francis
2019-06-27 13:15 ` Adhemerval Zanella
2019-07-03 23:52 ` Alistair Francis
2019-07-24 20:22 ` Joseph Myers
2019-07-24 23:03 ` Alistair Francis
2019-07-25 12:57 ` Arnd Bergmann
2019-07-25 17:03 ` Paul Eggert
2019-07-25 17:21 ` Zack Weinberg
2019-07-25 18:53 ` Arnd Bergmann
2019-07-26 13:01 ` Florian Weimer
2019-07-26 13:08 ` Zack Weinberg
2019-07-25 21:23 ` Joseph Myers
2019-06-25 0:11 ` [RFC v2 13/20] RISC-V: Add path of library directories for the 32-bit Alistair Francis
2019-06-25 0:11 ` [RFC v2 12/20] RISC-V: Support dynamic loader " Alistair Francis
2019-06-25 0:11 ` [RFC v2 02/20] y2038: Provide conversion helpers for struct __timespec64 Alistair Francis
2019-06-25 0:12 ` [RFC v2 18/20] RISC-V: Build Infastructure for the 32-bit Alistair Francis
2019-06-25 0:12 ` [RFC v2 16/20] RISC-V: Regenerate ULPs of RISC-V Alistair Francis
2019-06-25 0:12 ` [RFC v2 20/20] Add RISC-V 32-bit target to build-many-glibcs.py Alistair Francis
2019-06-25 0:12 ` [RFC v2 09/20] sysdeps/getrlimit: Use prlimit64 if avaliable Alistair Francis
2019-06-25 11:11 ` Florian Weimer
2019-06-25 20:48 ` Alistair Francis
2019-06-25 21:10 ` Florian Weimer
2019-06-25 23:41 ` Alistair Francis
2019-06-25 0:12 ` [RFC v2 04/20] include/time.h: Fix conflicting timespec types on 32-bit Alistair Francis
2019-06-25 11:17 ` Arnd Bergmann
2019-06-25 22:23 ` Alistair Francis
2019-06-25 0:12 ` [RFC v2 15/20] RISC-V: Hard float support for the 32 bit Alistair Francis
2019-06-25 0:12 ` [RFC v2 17/20] RISC-V: Add ABI lists Alistair Francis
2019-06-25 0:12 ` [RFC v2 14/20] RISC-V: The ABI implementation for the 32-bit Alistair Francis
2019-06-25 0:12 ` [RFC v2 06/20] sysdeps/futex: Use futex_time64 if avaliable Alistair Francis
2019-06-25 11:14 ` Florian Weimer
2019-06-25 11:26 ` Andreas Schwab
2019-06-25 11:41 ` Arnd Bergmann
2019-06-25 12:07 ` Florian Weimer
2019-06-25 13:32 ` Arnd Bergmann
2019-06-25 0:12 ` [RFC v2 11/20] RISC-V: Use 64-bit time_t and off_t for RV32 and RV64 Alistair Francis
2019-06-25 0:12 ` [RFC v2 19/20] RISC-V: Fix llrint and llround missing exceptions on RV32 Alistair Francis
2019-06-25 0:12 ` [RFC v2 08/20] sysdeps/wait: Use waitid if avaliable Alistair Francis
2019-06-25 8:16 ` Andreas Schwab
2019-06-25 10:55 ` Zack Weinberg
2019-06-25 11:06 ` Florian Weimer
2019-06-25 12:01 ` Arnd Bergmann
2019-06-25 12:10 ` Florian Weimer
2019-06-25 13:30 ` Arnd Bergmann
2019-06-25 13:39 ` Arnd Bergmann
2019-06-25 13:47 ` Florian Weimer
2019-06-25 14:05 ` Arnd Bergmann
2019-06-25 14:08 ` Florian Weimer
2019-06-25 14:21 ` Arnd Bergmann
2019-06-25 14:29 ` Florian Weimer
2019-06-26 14:38 ` Arnd Bergmann
2019-06-26 15:48 ` Florian Weimer
2019-06-26 16:28 ` Andreas Schwab
2019-07-08 12:10 ` Florian Weimer
2019-07-08 12:34 ` Andreas Schwab
2019-07-08 12:37 ` Florian Weimer
2019-07-09 23:00 ` Alistair Francis
2019-07-10 7:34 ` Andreas Schwab
2019-07-10 17:51 ` Alistair Francis
2019-07-25 15:49 ` Joseph Myers
2019-06-26 21:08 ` Arnd Bergmann
2019-06-27 7:33 ` Florian Weimer
2019-06-27 8:25 ` Andreas Schwab
2019-06-27 10:21 ` Arnd Bergmann
2019-06-27 11:12 ` Florian Weimer
2019-06-27 15:24 ` Arnd Bergmann
2019-07-03 23:53 ` Alistair Francis
2019-06-25 23:54 ` Alistair Francis
2019-06-25 11:16 ` [RFC v2 00/20] RISC-V glibc port for the 32-bit Florian Weimer
2019-06-25 12:08 ` Arnd Bergmann
2019-07-04 8:47 ` Jim Wilson
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=20190627004931.79b99cdf@jawa \
--to=lukma@denx.de \
--cc=adhemerval.zanella@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=arnd@arndb.de \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=macro@wdc.com \
--cc=palmer@sifive.com \
--cc=zong@andestech.com \
--cc=zongbox@gmail.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).