Consensus from maintainers is that it's a mistake that this option is on
for riscv64, especially since compat is off.
** Also affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-starfive (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-allwinner (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner in Ubuntu.
https://bugs.launchpad.net/bugs/2038584
Title:
Turning COMPAT_32BIT_TIME off on riscv64
Status in linux package in Ubuntu:
Incomplete
Status in linux-allwinner package in Ubuntu:
New
Status in linux-riscv package in Ubuntu:
New
Status in linux-starfive package in Ubuntu:
New
Bug description:
This will prevent (?!) binaries to operate correctly, if they are
still using time32.... but maybe riscv32 ABI uses 64-bit time_t
anyway?
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic
failure in the field due to these syscalls enabled and used.
I would like to request if we can turn off COMPAT_32BIT_TIME on every
architecture, thus this will be arch by arch bug report, and arch by
arch decision.
This needs to be a per-arch decision, potentially taking into
consideration bi-arch userspace support.
config COMPAT_32BIT_TIME
bool "Provide system calls for 32-bit time_t"
default !64BIT || COMPAT
help
This enables 32 bit time_t support in addition to 64 bit time_t support.
This is relevant on all 32-bit architectures, and 64-bit architectures
as part of compat syscall handling.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
