From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jouni Malinen <j@w1.fi>
Cc: Jouni Malinen <jouni.malinen@atheros.com>,
wireless <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
John Linville <linville@tuxdriver.com>
Subject: Re: Regression in 2.6.27-git from commit 43ac2ca3840f64
Date: Wed, 22 Oct 2008 09:47:47 -0700 [thread overview]
Message-ID: <48FF5933.3080501@lwfinger.net> (raw)
In-Reply-To: <20081022072840.GD16005@jm.kir.nu>
Jouni Malinen wrote:
> On Tue, Oct 21, 2008 at 09:01:14AM -0700, Larry Finger wrote:
>
>> On my x86_64 system, the mainline 2.6.27-git kernel (v2.6.27-6030-g6da0b38)
>> shows the following anomaly with the 'iwlist scan' command:
>>
>> Cell 03 - Address: 00:14:BF:85:49:FA
>> ESSID:"lwfdjf"
>> Mode:Master
>> Channel:1
>> Frequency:2.412 GHz (Channel 1)
>> Quality=66/100 Signal level:-62 dBm Noise level=-68 dBm
>> Encryption key:on
>> IE: Unknown: 00066C7766646A66
>
> ...
>
>> This problem was bisected to commit 43ac2ca3840f64f699a239535c590fa7ebaaac27,
>> entitled "mac80211: Handle scan result IEs in one block". The same bug is
>> present in the wireless-testing tree.
>
> Problem? Bug? This is by design. What does not work for you?
When a utility starts spitting messages that it doesn't understand what the
kernel is providing _AND_ the commit message does not mention that this will
happen, can someone be blamed for thinking it is a bug?
Clearly this is not a regression. Are there plans to update the wireless utilities?
Larry
next prev parent reply other threads:[~2008-10-22 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 16:01 Regression in 2.6.27-git from commit 43ac2ca3840f64 Larry Finger
2008-10-21 21:30 ` Johannes Berg
2008-10-22 2:34 ` Larry Finger
2008-10-22 7:23 ` Johannes Berg
2008-10-21 21:37 ` John W. Linville
2008-10-22 2:45 ` Larry Finger
2008-10-22 7:28 ` Jouni Malinen
2008-10-22 16:47 ` Larry Finger [this message]
2008-10-22 17:04 ` Jouni Malinen
2008-10-22 17:06 ` Johannes Berg
2008-10-22 17:37 ` Jean Tourrilhes
2008-10-22 17:46 ` Johannes Berg
2008-10-22 18:00 ` Jean Tourrilhes
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=48FF5933.3080501@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=j@w1.fi \
--cc=jouni.malinen@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).