From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Pedersen <thomas@eero.com>, Greg Maitz <ghh19622@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Incorrect mesh path seq num
Date: Mon, 04 Sep 2017 15:19:33 +0200 [thread overview]
Message-ID: <1504531173.27801.0.camel@sipsolutions.net> (raw)
In-Reply-To: <CADjYELxyuT74Ms30Ohu_a6Ymg6RLctf6mehRmw-poLgLMZWiwQ@mail.gmail.com> (sfid-20170901_220755_362447_35ACB724)
On Fri, 2017-09-01 at 13:07 -0700, Thomas Pedersen wrote:
> On Thu, Aug 31, 2017 at 11:30 PM, Greg Maitz <ghh19622@gmail.com>
> wrote:
> > Hi guys,
> >
> > I'm seeing a problem when I work on the wireless mesh between two
> > linux devices. The root node has 3.18 kernel while the next hop
> > station runs 2.6.37 kernel. I found the mpath->sn value is
> > incorrect
> > most of the time on the device having 2.6.37 kernel. After
> > examining
> > the code, in function hwmp_route_info_get [mesh_hwmp.c], after
> > mesh_path_lookup, the sequence number (i.e, mpath->sn) is
> > incorrect.
> > For instance, I see mpath->sn having value 0x30950000. It should be
> > 0x9530, while the orig_sn is having value 0x9531.
>
> Looks like an endianess bug. Are you testing on two platforms of
> different endianess?
Even if that's the case, wouldn't it mean some kind of conversion is
missing somewhere?
johannes
next prev parent reply other threads:[~2017-09-04 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 6:30 Incorrect mesh path seq num Greg Maitz
2017-09-01 20:07 ` Thomas Pedersen
2017-09-04 13:19 ` Johannes Berg [this message]
2017-09-08 19:58 ` Thomas Pedersen
2018-05-07 4:40 ` Greg Maitz
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=1504531173.27801.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ghh19622@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@eero.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 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).