[RFC PATCH 3/4] linux: consistently use time64 syscalls if available
Arnd Bergmann
arnd@arndb.de
Wed Nov 11 13:57:17 GMT 2026
On Wed, Nov 11, 2026, at 14:56, Adhemerval Zanella Netto wrote:
> On 11/11/26 10:04, Arnd Bergmann wrote:
>> On Wed, Nov 11, 2026, at 13:09, Adhemerval Zanella Netto wrote:
>> I don't think that would work here, since we need both cases
>> depending on the expected kernel ABI version.
>>
>> - on __ASSUME_TIME64_SYSCALLS (building for new kernel versions)
>> we want __NR_ppoll_time64 and need to convert to __timespec64
>> - when building for older 32-bit kernels, the #ifndef is false
>> because both __NR_ppoll_time64 and __NR_ppoll are defined,
>> but we want to use __NR_ppoll with the time32 timespec.
>>
>>> Missing ')'. More importantly, tst-clone3.c and i386/tst-bz21269.c are
>>> regular tests
>>> and do not include <kernel-features.h>, so __ASSUME_TIME64_SYSCALLS is
>>> never defined there.
>>
>> Is it ok to include that header here it then, or does this need to
>> try call both syscalls?
>
> I think we can just mimic what the internal futex code itself does. I
> think we can
> eventually phase this out with my futex wrapper proposal.
Right, makes sense. Thanks,
Arnd
More information about the Libc-alpha
mailing list