[Bug 2035061] [NEW] uptime -p reports incorrect output after 52 weeks

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

[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

** Affects: procps (Ubuntu)
     Importance: Low
     Assignee: Robert Malz (rmalz)
         Status: New

** Affects: procps (Ubuntu Focal)
     Importance: Low
     Assignee: Robert Malz (rmalz)
         Status: New

** Affects: procps (Ubuntu Jammy)
     Importance: Low
     Assignee: Robert Malz (rmalz)
         Status: New


** Tags: patch se se-sponsor-dgadomski
-- 
uptime -p reports incorrect output after 52 weeks
https://bugs.launchpad.net/bugs/2035061
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.