From: Masashi Honma <masashi.honma@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iw: Fix bitrate output when no rate info found
Date: Tue, 14 Feb 2017 17:55:50 +0900 [thread overview]
Message-ID: <a2ffeab5-dd9c-1c9d-3fd1-c098a6d1e748@gmail.com> (raw)
In-Reply-To: <1487061321.4705.1.camel@sipsolutions.net>
On 2017-02-14 17:35, Johannes Berg wrote:
> On Tue, 2017-02-14 at 14:21 +0900, Masashi Honma wrote:
>> Previously, bitrate showed uninitialized buffer when no rate info
>> found.
>
> When would this happen?
I could see in mesh STA connection with 11n and legacy mixed.
STA A has disable_ht=1.
STA B has disable_ht=0.
> I'm not really sure this is right - perhaps we don't have
> RATE_INFO_BITRATE(32), but still have the MCS data?
I recognized there was a issue on such a case. I will send a patch to
wpa_supplicant. Anyway, showing string message is better than showing
raw binary data.
> How about we just add "(unknown)" or so and not return here?
Yes. First time, I supposed to use "unknown". But in the function
parse_bitrate(), nla_parse_nested() returns message "failed to parse
nested rate attributes!". This explains why the bitrate is unknown. So I
used explaining message. We could see the message like this.
tx bitrate: No rate info found!
rx bitrate: 48.0 MBit/s
Masashi Honma.
next prev parent reply other threads:[~2017-02-14 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 5:21 [PATCH] iw: Fix bitrate output when no rate info found Masashi Honma
2017-02-14 5:26 ` Masashi Honma
2017-02-14 8:35 ` Johannes Berg
2017-02-14 8:55 ` Masashi Honma [this message]
2017-02-14 9:14 ` Johannes Berg
2017-02-14 9:35 ` Masashi Honma
2017-02-14 9:38 ` [PATCH v2] " Masashi Honma
2017-02-14 9:45 ` 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=a2ffeab5-dd9c-1c9d-3fd1-c098a6d1e748@gmail.com \
--to=masashi.honma@gmail.com \
--cc=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox