netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Wrong use of MAX_JIFFY_OFFSET?
@ 2012-03-27  1:25 Liu Yu
  2012-03-27  8:54 ` David Laight
  0 siblings, 1 reply; 2+ messages in thread
From: Liu Yu @ 2012-03-27  1:25 UTC (permalink / raw)
  To: netdev

Hi guys,

I saw a couple of places in current kernel have this kind of code:

> static inline unsigned int elapsed_jiffies_msecs(unsigned long start)
> {
>         unsigned long end = jiffies;
>
>         if (end >= start)
>                return jiffies_to_msecs(end - start);
>
>         return jiffies_to_msecs(end + (MAX_JIFFY_OFFSET - start) + 1);
> }

As you know, jiffies has a type of unsigned long, so if we know which is the
end and
which is the start, then (end - start) can simply figure out how much
jiffies flies,
without worry about the overflow.

Look at the code above, assume that there is just an overflow happening on
jiffies: end=0 and start=~0UL.
Since end < start, then the return value of the function is
jiffies_to_msecs(MAX_JIFFY_OFFSET+2).
But shouldn't the correct value be jiffies_to_msecs(1)?

could someone tell me that am I missing anything?

Thanks,
Yu

^ permalink raw reply	[flat|nested] 2+ messages in thread

* RE: Wrong use of MAX_JIFFY_OFFSET?
  2012-03-27  1:25 Wrong use of MAX_JIFFY_OFFSET? Liu Yu
@ 2012-03-27  8:54 ` David Laight
  0 siblings, 0 replies; 2+ messages in thread
From: David Laight @ 2012-03-27  8:54 UTC (permalink / raw)
  To: Liu Yu, netdev

 

> -----Original Message-----
> From: netdev-owner@vger.kernel.org 
> [mailto:netdev-owner@vger.kernel.org] On Behalf Of Liu Yu
> Sent: 27 March 2012 02:25
> To: netdev@vger.kernel.org
> Subject: Wrong use of MAX_JIFFY_OFFSET?
> 
> Hi guys,
> 
> I saw a couple of places in current kernel have this kind of code:
> 
> > static inline unsigned int elapsed_jiffies_msecs(unsigned 
> long start)
> > {
> >         unsigned long end = jiffies;
> >
> >         if (end >= start)
> >                return jiffies_to_msecs(end - start);
> >
> >         return jiffies_to_msecs(end + (MAX_JIFFY_OFFSET - 
> start) + 1);
> > }
> 
> As you know, jiffies has a type of unsigned long, so if we 
> know which is the end and
> which is the start, then (end - start) can simply figure out how much
> jiffies flies, without worry about the overflow.
> 
> Look at the code above, assume that there is just an overflow 
> happening on
> jiffies: end=0 and start=~0UL.
> Since end < start, then the return value of the function is
> jiffies_to_msecs(MAX_JIFFY_OFFSET+2).
> But shouldn't the correct value be jiffies_to_msecs(1)?
> 
> could someone tell me that am I missing anything?

That code has confused me...
MAX_JIFFIES_OFFSET appears to have something to do with
timespec_to_jiffies() rather than being anything to so with
the way 'jiffies' itself wraps.

Since arithmetic wrap is well defined for unsigned values
the correct code should just be:
	return jiffies_to_ms(jiffies - start);
The code above is completly fubar when jiffies wraps.

	David

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-03-27  8:56 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-27  1:25 Wrong use of MAX_JIFFY_OFFSET? Liu Yu
2012-03-27  8:54 ` David Laight

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).