mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* /proc/uptime overrun
@ 2003-03-24 10:48 Tom
  0 siblings, 0 replies; only message in thread
From: Tom @ 2003-03-24 10:48 UTC (permalink / raw)
  To: linux-kernel

(no maintainer for proc listed in MAINTAINERS)


[1.] One line summary of the problem:    
/proc/uptime overrun, resetting uptime counter to 0

[2.] Full description of the problem/report:
uptime is stored in an unsigned long int in fs/proc/proc_misc.c (around
line 121), set from jiffies defined in include/sched.h. 
On systems available to me, HZ is always 100, which makes this value 
overrun the unsigned long after about 497 days.

[3.] Keywords (i.e., modules, networking, kernel):
kernel, proc

[4.] Kernel version (from /proc/version):
found on a 2.4.12, but apparently still there in 2.4.19


[5.] Output of Oops.. message (if applicable) with symbolic information 
     resolved (see Documentation/oops-tracing.txt)
(no oops)

[6.] A small shell script or example program which triggers the
     problem (if possible)
#!/bin/sh
sleep 498d
cat /proc/uptime

[7.] Environment
(not considered relevant)

[X.] Other notes, patches, fixes, workarounds:
No, I don't consider this very important. However, the wrong uptime
display may trigger a search for a power failure or system compromise.
Did for me.


-- 
PGP/GPG key: http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-03-24 10:37 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-24 10:48 /proc/uptime overrun Tom

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®