linux-kernel - Re: [PATCH] ath: sanitize 0xFFFF regdomain

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-next>] [day] [month] [year] [list]

Message-ID: <CAB=NE6WAKjktv8G1eikkfkbB7KAa_XefJj-udfH8b_vvgLbznQ@mail.gmail.com>
Date:	Tue, 26 Feb 2013 10:29:43 -0800
From:	"Luis R. Rodriguez" <mcgrof@....qualcomm.com>
To:	Michal Kazior <kazikcz@...il.com>,
	David Quan <dquan@....qualcomm.com>,
	linux-kernel@...r.kernel.org
Cc:	linux-wireless@...r.kernel.org
Subject: Re: [PATCH] ath: sanitize 0xFFFF regdomain

On Sat, Feb 23, 2013 at 11:34 AM, Michal Kazior <kazikcz@...il.com> wrote:
> Dbii F52N-PRO mini pci device reports an invalid
> regdomain. This card has been reported to work on
> MikroTik's RouterOS but failed on Linux:
>
> [   14.320000] ath: EEPROM regdomain: 0xffff
> [   14.320000] ath: EEPROM indicates we should expect a country code
> [   14.320000] ath: invalid regulatory domain/country code 0xbfff
> [   14.320000] ath: Invalid EEPROM contents
> [   14.320000] ath9k 0000:00:12.0: Failed to initialize device
> [   14.330000] ath9k: probe of 0000:00:12.0 failed with error -22
>
> With the patch the device works fine.
>
> Signed-off-by: Michal Kazior <kazikcz@...il.com>

NACK. This comes up every now and then and this is not a valid device
ID, this is an issue with the card, so what you can do is adjust the
device ID post bootup. Not sure if distros have an easy way to set
this up, if not perhaps this should be considered as this has come up
twice before.

  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/