All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] Use proper casting with signed timespec.tv_nsec values
Date: Thu, 01 Sep 2005 18:14:33 -0700	[thread overview]
Message-ID: <4317A779.7090400@mvista.com> (raw)
In-Reply-To: <1125608627.22448.4.camel@cog.beaverton.ibm.com>

john stultz wrote:
> All,
> 	I recently ran into a bug with an older kernel where xtime's tv_nsec
> field had accumulated more then 2 seconds worth of time. The timespec's
> tv_nsec is a signed long, however gettimeofday() treats it as an
> unsigned long. Thus when the failure occured, very strange and difficult
> to debug time problems occurred.
> 
> The main cause of the problem I was seeing is already fixed in mainline,
> however just to be safe, I figured the following patch would be wise.
> 
> I only audited i386 and x86_64, however other arches probably could have
> similar signed problems as well.
> 
> Please let me know if you have any further comments or feedback.

John,

There is a problem in the way this code handles the conversion to usec. 
  There is a conversion here and also in the get_offset code.  If the 
nanoseconds are carrier until after the addition of the two about 25% of 
the time you will end up with an additional usec in time.  I strongly 
suggest changing to convert to usec after the addition of xtime and 
get_offset time to avoid this.  If the "correct" thing is done in 
clock_gettime() (i.e. get_offset is in nanoseconds) this actually turns 
up as a back step in time WRT gettimeofday and clock_gettime().

George
-- 
> 
> thanks
> -john
> 
> linux-2.6.13_signed-tv_nsec_A0.patch
> ====================================
> diff --git a/arch/i386/kernel/time.c b/arch/i386/kernel/time.c
> --- a/arch/i386/kernel/time.c
> +++ b/arch/i386/kernel/time.c
> @@ -156,7 +156,7 @@ void do_gettimeofday(struct timeval *tv)
>  			usec += lost * (USEC_PER_SEC / HZ);
>  
>  		sec = xtime.tv_sec;
> -		usec += (xtime.tv_nsec / 1000);
> +		usec += (unsigned long)xtime.tv_nsec / 1000;
>  	} while (read_seqretry(&xtime_lock, seq));
>  
>  	while (usec >= 1000000) {
> diff --git a/arch/x86_64/kernel/time.c b/arch/x86_64/kernel/time.c
> --- a/arch/x86_64/kernel/time.c
> +++ b/arch/x86_64/kernel/time.c
> @@ -128,7 +128,7 @@ void do_gettimeofday(struct timeval *tv)
>  		seq = read_seqbegin(&xtime_lock);
>  
>  		sec = xtime.tv_sec;
> -		usec = xtime.tv_nsec / 1000;
> +		usec = (unsigned long)xtime.tv_nsec / 1000;
>  
>  		/* i386 does some correction here to keep the clock 
>  		   monotonous even when ntpd is fixing drift.
> diff --git a/kernel/timer.c b/kernel/timer.c
> --- a/kernel/timer.c
> +++ b/kernel/timer.c
> @@ -824,7 +824,7 @@ static void update_wall_time(unsigned lo
>  	do {
>  		ticks--;
>  		update_wall_time_one_tick();
> -		if (xtime.tv_nsec >= 1000000000) {
> +		if ((unsigned long)xtime.tv_nsec >= 1000000000) {
>  			xtime.tv_nsec -= 1000000000;
>  			xtime.tv_sec++;
>  			second_overflow();
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
George Anzinger   george@mvista.com
HRT (High-res-timers):  http://sourceforge.net/projects/high-res-timers/

  parent reply	other threads:[~2005-09-02  1:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01 21:03 [RFC][PATCH] Use proper casting with signed timespec.tv_nsec values john stultz
2005-09-01 21:37 ` Eric Dumazet
2005-09-01 22:25   ` john stultz
2005-09-02  1:14 ` George Anzinger [this message]
2005-09-06 17:33 ` Christoph Lameter
2005-09-06 19:54   ` john stultz

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=4317A779.7090400@mvista.com \
    --to=george@mvista.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.