[PATCH v3 0/3] Add support for y2038 safe syscalls
Alistair Francis
Alistair.Francis at wdc.com
Tue Sep 24 20:54:31 UTC 2019
On Wed, 2019-09-18 at 09:28 -0700, Alistair Francis wrote:
> Busybox currently manually calls the clock_gettime syscall in some
> cases. This causes breakages on y2038 safe 32-bit architectures such
> as
> 32-bit RISC-V. To fix this breakage let's add some #ifdefs around the
> syscalls to call the __NR_clock_gettime64 if we don't have
> __NR_clock_gettime defined and time_t is 64-bits.
Ping!
Alistair
>
> v3:
> - Rebase on master
> v2:
> - Fix comment typo
>
> Alistair Francis (3):
> date: Use 64 prefix syscall if we have to
> time: Use 64 prefix syscall if we have to
> runsv: Use 64 prefix syscall if we have to
>
> coreutils/date.c | 11 +++++++++--
> libbb/time.c | 7 +++++++
> runit/runsv.c | 7 +++++++
> 3 files changed, 23 insertions(+), 2 deletions(-)
>
More information about the busybox
mailing list