IBM Z are deployed for longer timeframes than usually anticipated. And I don't think we will ever be able to get a straight answer about this.
I am proposing to turn off both COMPAT and COMPAT_32BIT_TIME on s390x in noble. If any useful production instances of software are identified that require either of these; and cannot run on Jammy, or in a VM, I will gladly SRU kernel config change to turn either or both of these options back on in noble. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038583 Title: Turning COMPAT_32BIT_TIME off on s390x Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This will prevent existing s390 binaries to operate correctly, if they are still using 32bit time. 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-z-systems/+bug/2038583/+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
