mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: linux-kernel@vger.kernel.org
Subject: /proc/uptime overrun
Date: Mon, 24 Mar 2003 11:48:09 +0100	[thread overview]
Message-ID: <20030324114809.A11393@lemuria.org> (raw)

(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

                 reply	other threads:[~2003-03-24 10:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030324114809.A11393@lemuria.org \
    --to=tom@lemuria.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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®