From: George Anzinger <george@mvista.com>
To: john stultz <johnstul@us.ibm.com>
Cc: Herbert Poetzl <herbert@13thfloor.at>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: do_posix_clock_monotonic_gettime() returns negative nsec
Date: Fri, 03 Dec 2004 00:43:53 -0800 [thread overview]
Message-ID: <41B02749.70900@mvista.com> (raw)
In-Reply-To: <1102042850.13294.43.camel@cog.beaverton.ibm.com>
john stultz wrote:
> On Thu, 2004-12-02 at 18:03, Herbert Poetzl wrote:
>
>>recent kernels (tested 2.6.10-rc2 and 2.6.10-rc2-bk15)
>>produce funny output in /proc/uptime like this:
>>
>> # cat /proc/uptime
>> 12.4294967218 9.05
>> # cat /proc/uptime
>> 13.4294967251 10.33
>> # cat /proc/uptime
>> 14.4294967295 11.73
>>
>>a short investigation of the issue, ended at
>>do_posix_clock_monotonic_gettime() which can (and
>>often does) return negative nsec values (within
>>one second), so while the actual 'time' returned
>>is correct, some parts of the kernel assume that
>>those part is within the range (0 - NSEC_PER_SEC)
>>
>> len = sprintf(page,"%lu.%02lu %lu.%02lu\n",
>> (unsigned long) uptime.tv_sec,
>> (uptime.tv_nsec / (NSEC_PER_SEC / 100)),
>>
>>as the function itself corrects overflows, it would
>>make sense to me to correct underflows too, for
>>example with the following patch:
>>
>>--- ./kernel/posix-timers.c.orig 2004-11-19 21:11:05.000000000 +0100
>>+++ ./kernel/posix-timers.c 2004-12-03 02:23:56.000000000 +0100
>>@@ -1208,7 +1208,10 @@ int do_posix_clock_monotonic_gettime(str
>> tp->tv_sec += wall_to_mono.tv_sec;
>> tp->tv_nsec += wall_to_mono.tv_nsec;
>>
>>- if ((tp->tv_nsec - NSEC_PER_SEC) > 0) {
>>+ if (tp->tv_nsec < 0) {
>>+ tp->tv_nsec += NSEC_PER_SEC;
>>+ tp->tv_sec--;
>>+ } else if ((tp->tv_nsec - NSEC_PER_SEC) > 0) {
>> tp->tv_nsec -= NSEC_PER_SEC;
>> tp->tv_sec++;
>> }
>
>
> Sounds like its a good fix to me.
>
> George: You have any comment?
Two, in fact. First, the result here is the sum of wall_to_monotonic and
getnstimeofday(). If nsec < 0, one or more of these must be also. Both of
these values are SUPPOSED to be normalized.
Second, I would rather see:
set_normalized_timespec(tp, tp->tv_sec + wall_to_mono.tv_sec,
tp->tv_nsec + wall_to_mono.tv_nsec);
Still, doing this paves over the first issue....
>
> thanks
> -john
>
>
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
next prev parent reply other threads:[~2004-12-03 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 2:03 do_posix_clock_monotonic_gettime() returns negative nsec Herbert Poetzl
2004-12-03 3:00 ` john stultz
2004-12-03 8:43 ` George Anzinger [this message]
2004-12-03 8:56 ` Andrew Morton
2004-12-03 3:08 ` Andrew Morton
2004-12-03 3:20 ` Herbert Poetzl
2004-12-03 8:53 ` George Anzinger
2004-12-03 17:22 ` Herbert Poetzl
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=41B02749.70900@mvista.com \
--to=george@mvista.com \
--cc=akpm@osdl.org \
--cc=herbert@13thfloor.at \
--cc=johnstul@us.ibm.com \
--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