Ubuntu
procps package

  1. Bug #2035061
  2. Comment #0

Comment 0 for bug 2035061

Revision history for this message
Robert Malz (rmalz) wrote :

[IMPACT]

uptime will provide incorrect data after 52 weeks. This is at least confusing for users utilizing this tool.
Issue is already fixed in upstream https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749.
Latest procps releases already include this patch (procps 4.0.3 lunar/mantic)
The fix is needed for following set of packages:
procps | 2:3.3.17-6ubuntu2 | jammy
procps | 2:3.3.16-1ubuntu2 | focal

[TEST CASE]

UPTIME="31528920 31528800"; mkfifo uptime_fifo; while true; do cat <<<$UPTIME > uptime_fifo; done & sudo mount -obind uptime_fifo /proc/uptime
uptime -p
Running above commands will result in incorrect uptime output.

[REGRESSION POTENTIAL]

The patch is already available in upstream, lunar/mantic releases already include is as well.

[OTHER]
Bug upstream: https://gitlab.com/procps-ng/procps/-/issues/217
Following patch is needed for older releases: https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749