netdev - Re: pull request: wireless-next 2014-02-20

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

Message-Id: <20140220.172922.864207706999214682.davem@davemloft.net>
Date:	Thu, 20 Feb 2014 17:29:22 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	linville@...driver.com
Cc:	linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: pull request: wireless-next 2014-02-20

From: "John W. Linville" <linville@...driver.com>
Date: Thu, 20 Feb 2014 15:30:05 -0500

> Please pull this batch of wireless updates intended for the 3.15
> stream!
> 
> For the mac80211 bits, Johannes says:
> 
> "We have some cleanups and minor fixes as well as userspace API
> improvements from a lot of people, extended VHT support for radiotap
> from Emmanuel, CSA improvements from Andrei, Luca and Michal. I've also
> included my work on hwsim to make dynamic registration of radios
> possible."
> 
> Along with that, we get the usual round of updates to ath9k,
> brcmfmac, mwifiex, wcn36xx, and the ti drivers -- nothing particularly
> noteworthy, mostly just random updates and refactoring.
> 
> Also included is a pull of the wireless tree, intended to resolve
> some potential merge issues.
> 
> Please let me know if there are problems!

Pulled, but please address this:

drivers/staging/rtl8821ae/rtl8821ae/trx.c: In function ‘rtl8821ae_rx_query_desc’:
drivers/staging/rtl8821ae/rtl8821ae/trx.c:619:3: warning: passing argument 1 of ‘ieee80211_is_robust_mgmt_frame’ from incompatible pointer type [enabled by default]

I was going to do the easy transformation to the "_" prefixed variant
but noticed that this code doesn't validate the skb length, which is
precisely the reason why this routine now takes an skb.