From: Johannes Berg <johannes@sipsolutions.net>
Date: Mon, 30 Nov 2015 11:30:58 +0100
Subject: [ath9k-devel] [PATCH v2 4/8] cfg80211: reg: Properly handle
 rules for 5 and 10 MHz channels
In-Reply-To: <20151130095652.GA7054@w1.fi>
	(sfid-20151130_105700_562689_2529B730)
References: <1448303241-27747-1-git-send-email-sojkam1@fel.cvut.cz>
	<1448303241-27747-5-git-send-email-sojkam1@fel.cvut.cz>
	<20151130095652.GA7054@w1.fi> (sfid-20151130_105700_562689_2529B730)
Message-ID: <1448879458.3957.1.camel@sipsolutions.net>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

On Mon, 2015-11-30 at 11:56 +0200, Jouni Malinen wrote:
> On Mon, Nov 23, 2015 at 07:27:17PM +0100, Michal Sojka wrote:
> > Regulatory rules are applied to channels as if the channel is at
> > least
> > 20 MHz wide. This is a problem when dealing with 5 and 10 MHz
> > channels
> > because side channels of a regulatory rule get disabled even when
> > they
> > fall into rule's frequency range.
> > 
> > This problem was already fixed in commit
> > 4edd56981c8fbb349b1529a2feaf772636eb1c83, but only for custom
> > regulatory
> > domains provided by drivers. Here we fix it also for all other
> > (e.g.
> > user-supplied) regulatory domains.
> > 
> > Before that, similar commit was
> > reverted (e33e2241e272eddc38339692500bd1c7d8753a77) due to it
> > allowing
> > running AP on channel 12 in the US regulatory domain.
> 
> I'm afraid this new patch needs to be reverted as well since it
> allows active scanning on channel 12 in the US regulatory domain.
> I.e., every full scan with this commit included results in a Probe
> Request frame being sent on channel 12..
> 

I've dropped it from my tree.

johannes