Add support for io_pgetevents_time64 syscall
authorAlistair Francis <alistair.francis@wdc.com>
Thu, 29 Aug 2019 20:56:21 +0000 (13:56 -0700)
committerPauli <paul.dale@oracle.com>
Wed, 18 Sep 2019 06:49:39 +0000 (16:49 +1000)
commit5b5e2985f355c8e99c196d9ce5d02c15bebadfbc
tree80b49adcd661ccbc7bd02ce546043bf904d6128d
parentf22431f2cd9e96cf75fd020c6e5019ff58f710cf
Add support for io_pgetevents_time64 syscall

32-bit architectures that are y2038 safe don't include syscalls that use
32-bit time_t. Instead these architectures have suffixed syscalls that
always use a 64-bit time_t. In the case of the io_getevents syscall the
syscall has been replaced with the io_pgetevents_time64 syscall instead.

This patch changes the io_getevents() function to use the correct
syscall based on the avaliable syscalls and the time_t size. We will
only use the new 64-bit time_t syscall if the architecture is using a
64-bit time_t. This is to avoid having to deal with 32/64-bit
conversions and relying on a 64-bit timespec struct on 32-bit time_t
platforms. As of Linux 5.3 there are no 32-bit time_t architectures
without __NR_io_getevents. In the future if a 32-bit time_t architecture
wants to use the 64-bit syscalls we can handle the conversion.

This fixes build failures on 32-bit RISC-V.

Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Paul Dale <paul.dale@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/9819)
engines/e_afalg.c