From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Fixing wrap-around bug in vis
Date: Fri, 12 Mar 2010 21:57:40 +0100 [thread overview]
Message-ID: <20100312205740.GA20427@pandem0nium> (raw)
In-Reply-To: <201003112306.48652.sven.eckelmann@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]
Hey,
nice catch!
I'd like to join the party and propose this version:
#define seq_before(x,y) ((int8_t) (x - y) < 0)
#define seq_after(x,y) seq_before(y,x)
Not so much bitshifting and may a little bit easier to
understand, but also not general and does not pass Svens regression test ... :(
Wrong seq_before(0, 128) == true
Wrong seq_after(0, 128) == true
Wrong seq_before(1, 129) == true
Wrong seq_after(1, 129) == true
Wrong seq_before(2, 130) == true
Wrong seq_after(2, 130) == true
Wrong seq_before(3, 131) == true
Wrong seq_after(3, 131) == true
Wrong seq_before(4, 132) == true
Wrong seq_after(4, 132) == true
Wrong seq_before(5, 133) == true
Wrong seq_after(5, 133) == true
What do you think? ;)
best regards
Simon
On Thu, Mar 11, 2010 at 11:06:42PM +0100, Sven Eckelmann wrote:
> Linus Lüssing wrote:
> > - if (vis_packet->seqno - old_info->packet.seqno <= 0) {
> > + if (vis_packet->seqno - old_info->packet.seqno
> > + <= 1 << 7 * sizeof(vis_packet->seqno)) {
>
> Shouldn't that be
> 1 << 7 + 8 * (sizeof(vis_packet->seqno) - 1))?
>
> Otherwise you would have left the the sizeof(vis_packet->seqno) most
> significant bits 0 and the rest one. And maybe a seq_before/seq_after static
> inline function could be created to make this thing a lot more readable. You
> could also do that in a macro if you don't want to assume the type of
> vis_packet->seqno... which is probably what you tried by using sizeof
>
> #define seq_before(x,y) ((x - y) >= 1 << 7 + 8 * (sizeof(x) - 1))
> #define seq_after(x,y) ((y - x) >= 1 << 7 + 8 * (sizeof(x) - 1))
> ....
>
> And maybe you see here that the equal part which is needed bellow that line
> isn't possible. So it must be changed to
>
> if (!seq_after(vis_packet->seqno, old_info->packet.seqno))
>
> I hope that this is right - please check twice.
>
>
> Best regards,
> Sven
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-03-12 20:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 23:03 [B.A.T.M.A.N.] vis: (sometimes) missing entries Linus Lüssing
2010-03-11 16:38 ` [B.A.T.M.A.N.] [PATCH] batman-adv: Fixing wrap-around bug in vis Linus Lüssing
2010-03-11 17:14 ` Linus Lüssing
2010-03-11 21:19 ` Linus Lüssing
2010-03-11 21:41 ` Linus Lüssing
2010-03-11 22:06 ` Sven Eckelmann
2010-03-11 22:33 ` Sven Eckelmann
2010-03-11 23:04 ` Sven Eckelmann
2010-03-12 0:09 ` Linus Lüssing
2010-03-12 7:45 ` Andrew Lunn
2010-03-12 9:04 ` Sven Eckelmann
2010-03-12 15:16 ` Sven Eckelmann
2010-03-12 19:09 ` Sven Eckelmann
2010-03-14 15:46 ` Linus Lüssing
2010-03-14 17:51 ` Marek Lindner
2010-03-12 20:57 ` Simon Wunderlich [this message]
2010-03-12 21:06 ` Sven Eckelmann
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=20100312205740.GA20427@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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