From: Johannes Berg <johannes@sipsolutions.net>
To: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [WEXT]: multiple calls for SIOCGIWSTATS return same value
Date: Mon, 08 Jun 2015 09:18:06 +0200 [thread overview]
Message-ID: <1433747886.2106.5.camel@sipsolutions.net> (raw)
In-Reply-To: <20150606203721.28791bb3@erg.abdn.ac.uk> (sfid-20150607_044726_833751_BC9D05B3)
On Sat, 2015-06-06 at 20:37 -0600, Gerrit Renker wrote:
> A problem has been found in recent kernels where multiple
> calls using SIOCGIWSTATS return the same, identical value.
Which "value"? I believe these return a number of different values. What
are the returned values? Are they perhaps just 0?
Is the application a 32-bit application running on a 64-bit machine
perhaps? There have been bugs in that area in the past, though I don't
believe anything changed between 3.19 and 4.0. In fact, in wext nothing
really changed at all - only some internal maintenance (commit
319090bf6c75e3ad42a8c74973be5e78ae4f948f)
> This behaviour is observable both using 'iwconfig <dev>'
> and wavemon info screen, where it was reported in [1].
>
> It looks as if this is a WEXT issue, since on the same
> system multiple 'iw dev <devname> station dump' calls
> return different signal level values.
>
> I can confirm the behaviour on davem 4.1.0-rc6 net tree
> at commit c46a024ea5, it has been reported on [1] for
> fedora 21 with kernel-4.0.4-201/2 as well.
>
> That report also stated that the behaviour does not occur
> on kernel-3.19.7-200. Have not had time to bisect yet.
>
> Thanks for any hints that can help resolve this.
I have no idea, sorry.
johannes
next prev parent reply other threads:[~2015-06-08 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 2:37 [WEXT]: multiple calls for SIOCGIWSTATS return same value Gerrit Renker
2015-06-08 7:18 ` Johannes Berg [this message]
2015-06-09 1:58 ` Gerrit Renker
2015-06-09 7:33 ` Johannes Berg
2015-06-10 2:25 ` Gerrit Renker
2015-06-10 6:12 ` Johannes Berg
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=1433747886.2106.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gerrit@erg.abdn.ac.uk \
--cc=linux-wireless@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.