linux-kernel - Re: [PATCH 1/4] cfg80211: Add attributes describing prohibited channel bandwidth

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]

Date:	Tue, 08 Apr 2014 11:54:46 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Rostislav Lisovy <lisovy@...il.com>
Cc:	"John W. Linville" <linville@...driver.com>,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
	Michal Sojka <sojkam1@....cvut.cz>, s.sander@...dsys.de,
	jan-niklas.meier@...kswagen.de,
	Rostislav Lisovy <rostislav.lisovy@....cvut.cz>
Subject: Re: [PATCH 1/4] cfg80211: Add attributes describing prohibited
 channel bandwidth

On Wed, 2014-04-02 at 15:31 +0200, Rostislav Lisovy wrote:
> Since there are frequency bands (e.g. 5.9GHz) allowing channels
> with only 10 or 5 MHz bandwidth, this patch adds attributes that
> allow keeping track about this information.
> 
> When channel attributes are reported to user-space, make sure to
> not break old tools, i.e. if the 'split wiphy dump' is enabled,
> report the extra attributes (if present) describing the bandwidth
> restrictions.  If the 'split wiphy dump' is not enabled,
> completely omit those channels that have flags set to either
> IEEE80211_CHAN_NO_10MHZ or IEEE80211_CHAN_NO_20MHZ.

I think you should probably squash patches 1 and 2, since otherwise you
could use the new channels?

Anyway, the patches don't seem to apply on mac80211-next, please rebase.

johannes

--
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/