From: Andreas Dilger <adilger@turbolabs.com>
To: "David S. Miller" <davem@redhat.com>
Cc: tim@physik3.uni-rostock.de, jgarzik@mandrakesoft.com,
andrewm@uow.edu.au, linux-kernel@vger.kernel.org,
torvalds@transmeta.com, netdev@oss.sgi.com, ak@muc.de,
kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH] net/ipv4/*, net/core/neighbour.c jiffies cleanup
Date: Wed, 7 Nov 2001 21:32:18 -0700 [thread overview]
Message-ID: <20011107213218.U5922@lynx.no> (raw)
In-Reply-To: <Pine.LNX.4.30.0111080003320.29364-100000@gans.physik3.uni-rostock.de> <20011107.160950.57890584.davem@redhat.com> <20011107173626.S5922@lynx.no> <20011107.164426.35502643.davem@redhat.com>
In-Reply-To: <20011107.164426.35502643.davem@redhat.com>; from davem@redhat.com on Wed, Nov 07, 2001 at 04:44:26PM -0800
On Nov 07, 2001 16:44 -0800, David S. Miller wrote:
> Why do they these cases that are actually in the code need to cast to
> a signed value to get a correct answer? They are not like your
> example.
>
> Almost all of these cases are:
>
> (jiffies - SOME_VALUE_KNOWN_TO_BE_IN_THE_PAST) > 5 * HZ
>
> So you say if we don't cast to signed, this won't get it right on
> wrap-around? I disagree, let's say "long" is 32-bits and jiffies
> wrapped around to "0x2" and SOME_VALUE... is 0xfffffff8. The
> subtraction above yields 10, and that is what we want.
OK, in this code it mostly appears that the wraparound is correct, but
in some cases it is very hard to say without specific knowledge of the code:
neigh->confirmed = jiffies - (n->parms->base_reachable_time<<1);
.
.
.
if ((state&NUD_VALID) &&
now - neigh->confirmed < neigh->parms->reachable_time) {
How are we to know that the above calculation won't be wrong because of
jiffies wrap?
> Please show me a bad case where casting to signed is necessary.
I don't know enough about the net code to say for sure, but for example
in drivers/sound/sb_common.c:
limit = jiffies + HZ / 10; /* Timeout */
for (i = 0; i < 500000 && (limit-jiffies)>0; i++)
Since limit and jiffies are both unsigned, the value will always be > 0,
unless they are equal.
> I actually ran through the tree the other night myself starting to
> convert these things, then I noticed that I couldn't even convince
> myself that the code was incorrect.
I don't disagree that it is possible to make correct code without the
macros, but it is easier to guarantee that it IS correct with the macros.
Rather than evaluate each jiffies usage on a case-by-case basis, it is
much easier to do a code audit and fix all comparisons. I don't see that
it harms anything to use the macros instead.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-08 4:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 0:00 [PATCH] net/ipv4/*, net/core/neighbour.c jiffies cleanup Tim Schmielau
2001-11-08 0:09 ` David S. Miller
2001-11-08 0:36 ` Andreas Dilger
2001-11-08 0:44 ` David S. Miller
2001-11-08 0:58 ` Tim Schmielau
2001-11-08 1:09 ` David S. Miller
2001-11-08 1:20 ` Tim Schmielau
2001-11-08 1:36 ` David S. Miller
2001-11-08 4:32 ` Andreas Dilger [this message]
2001-11-08 4:39 ` David S. Miller
2001-11-08 1:22 ` Linus Torvalds
2001-11-08 17:54 ` kuznet
2001-11-08 18:10 ` Tim Schmielau
2001-11-08 18:10 ` Andreas Dilger
2001-11-08 18:32 ` kuznet
-- strict thread matches above, loose matches on Subject: below --
2001-11-08 3:07 Krishna Kumar
2001-11-08 5:26 ` Linus Torvalds
2001-11-08 16:55 Krishna Kumar
2001-11-08 17:10 ` Linus Torvalds
2001-11-08 18:01 ` Andreas Dilger
2001-11-09 10:43 ` Vino Thomas
2001-11-08 17:47 Krishna Kumar
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=20011107213218.U5922@lynx.no \
--to=adilger@turbolabs.com \
--cc=ak@muc.de \
--cc=andrewm@uow.edu.au \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=tim@physik3.uni-rostock.de \
--cc=torvalds@transmeta.com \
/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.