linux-kernel - Re: WARNING at net/wireless/reg.c when wireless network is disconnected

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <AANLkTimPznW41N0aqkqjAKZdt73ugY2KBoRXFNPxuTOT@mail.gmail.com>
Date:	Thu, 5 Aug 2010 11:22:44 -0700
From:	"Luis R. Rodriguez" <lrodriguez@...eros.com>
To:	"John W. Linville" <linville@...driver.com>
Cc:	Thomas Bächler <thomas@...hlinux.org>,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
	Johannes Berg <johannes@...solutions.net>
Subject: Re: WARNING at net/wireless/reg.c when wireless network is 
	disconnected

On Wed, Aug 4, 2010 at 7:52 AM, John W. Linville <linville@...driver.com> wrote:
> On Wed, Aug 04, 2010 at 04:28:28PM +0200, Thomas Bächler wrote:
>> Am 04.08.2010 15:49, schrieb John W. Linville:
>> > On Wed, Aug 04, 2010 at 01:36:23PM +0200, Thomas Bächler wrote:
>> >> Hello,
>> >>
>> >> this warning has been around ever since I switched to 2.6.34, has
>> >> accompanied me through the 2.6.35-rc* phase and is still there with
>> >> 2.6.35. I didn't bother to report it so far, as there seems to be no harm.
>> >>
>> >> Whenever I disconnect/get disconnected from the wireless, I receive the
>> >> below warning:
>> >>
>> >> ------------[ cut here ]------------
>> >> WARNING: at net/wireless/reg.c:272
>> >> regulatory_hint_disconnect+0x1b3/0x230 [cfg80211]()
>> >> Hardware name: TECRA A11
>> >> Unexpected user alpha2: de
>> >
>> > Perhaps you need to set the regdomain as "DE" rather than "de"?
>> >
>> > John
>>
>> You are actually right. I did set it to "DE" with iw, but wpa_supplicant
>> had a setting country="de". I just fixed that and will soon see if the
>> problem disappears.
>>
>> Still, the warning shouldn't look like a bad kernel bug, but rather an
>> advisory to the user to set something sane. What confuses me even more
>> is that this has been set to DE afterwards:
>
> Perhaps we should just upcase the alpha2 value?  I'm not sure why we don't.

It just needs to be implemented.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/