Turning COMPAT_32BIT_TIME off on amd64
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| intel |
New
|
Undecided
|
Unassigned | ||
| linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
| linux-aws (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| linux-azure (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| linux-gcp (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| linux-ibm (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| linux-intel-iotg (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| linux-nvidia (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| linux-oracle (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
This will prevent existing i386 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.
| tags: | added: amd64 |
| Changed in linux (Ubuntu): | |
| milestone: | none → later |
| tags: | added: 32bit-time |
| tags: | added: y2038 |
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote Missing required logs. | #1 |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 2038579
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.