<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/net/wireless, branch v4.0</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v4.0</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v4.0'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2015-04-01T18:48:50Z</updated>
<entry>
<title>Merge tag 'wireless-drivers-for-davem-2015-04-01' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers</title>
<updated>2015-04-01T18:48:50Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2015-04-01T18:48:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f5f321c43150cb4db8f342c8479c6fbdbe20b338'/>
<id>urn:sha1:f5f321c43150cb4db8f342c8479c6fbdbe20b338</id>
<content type='text'>
Kalle Valo says:

====================
iwlwifi:

* fix a memory leak, we leaked memory each time the module
  was loaded.
====================

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge tag 'iwlwifi-for-kalle-2015-03-30' of https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes</title>
<updated>2015-03-30T06:39:12Z</updated>
<author>
<name>Kalle Valo</name>
<email>kvalo@codeaurora.org</email>
</author>
<published>2015-03-30T06:39:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=69628cd0652a091591ef44ac07c150063b789c4a'/>
<id>urn:sha1:69628cd0652a091591ef44ac07c150063b789c4a</id>
<content type='text'>
* fix a memory leak: we leaked memory each time the module
was loaded.
</content>
</entry>
<entry>
<title>Merge tag 'wireless-drivers-for-davem-2015-03-24' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers</title>
<updated>2015-03-24T19:15:55Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2015-03-24T19:15:55Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=e43e50524e6b00522cc7a1deee3eebd7046cde6f'/>
<id>urn:sha1:e43e50524e6b00522cc7a1deee3eebd7046cde6f</id>
<content type='text'>
iwlwifi:

* avoid panic with lots of IBSS stations
* Fix dvm's behavior after suspend resume
* Allow to keep connection after CSA failure
* Remove a noisy by harmless WARN_ON
* New device IDs

rtlwifi:

* fix IOMMU mapping leak in AP mode

brcmfmac:

* disable MBSS feature for BCM43362 to get AP mode working again

ath9k:

* disable Transmit Power Control (TPC) again due to regressions

* fix beaconing issue with AP+STA setup

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>iwlwifi: Fix memory leak in iwl_req_fw_callback()</title>
<updated>2015-03-24T09:40:36Z</updated>
<author>
<name>Larry Finger</name>
<email>Larry.Finger@lwfinger.net</email>
</author>
<published>2015-03-23T19:07:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a71aaf66725e8fc02253a3bbea15d27e656434fe'/>
<id>urn:sha1:a71aaf66725e8fc02253a3bbea15d27e656434fe</id>
<content type='text'>
In this routine, kzalloc allocates a memory block. This allocation is
freed in the error paths, but not in the normal exit, thus the allocation
is leaked.

The kmemleak facility was used to find the leak.

Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: Johannes Berg &lt;johannes.berg@intel.com&gt;
Cc: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
Cc: Intel Linux Wireless &lt;ilw@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'iwlwifi-for-kalle-2014-03-22' of https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes</title>
<updated>2015-03-23T04:43:43Z</updated>
<author>
<name>Kalle Valo</name>
<email>kvalo@codeaurora.org</email>
</author>
<published>2015-03-23T04:43:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=6ae4ccfee09efe5baa3951d1c1d27050a46a1469'/>
<id>urn:sha1:6ae4ccfee09efe5baa3951d1c1d27050a46a1469</id>
<content type='text'>
* avoid panic with lots of IBSS stations
* Fix dvm's behavior after suspend resume
* Allow to keep connection after CSA failure
* Remove a noisy by harmless WARN_ON
* New device IDs
</content>
</entry>
<entry>
<title>rtlwifi: Fix IOMMU mapping leak in AP mode</title>
<updated>2015-03-22T05:52:25Z</updated>
<author>
<name>Larry Finger</name>
<email>Larry.Finger@lwfinger.net</email>
</author>
<published>2015-03-21T20:16:05Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=be0b5e635883678bfbc695889772fed545f3427d'/>
<id>urn:sha1:be0b5e635883678bfbc695889772fed545f3427d</id>
<content type='text'>
Transmission of an AP beacon does not call the TX interrupt service routine,
which usually does the cleanup. Instead, cleanup is handled in a tasklet
completion routine. Unfortunately, this routine has a serious bug in that it does
not release the DMA mapping before it frees the skb, thus one IOMMU mapping is
leaked for each beacon. The test system failed with no free IOMMU mapping slots
approximately one hour after hostapd was used to start an AP.

This issue was reported and tested at https://github.com/lwfinger/rtlwifi_new/issues/30.

Reported-and-tested-by: Kevin Mullican &lt;kevin@mullican.com&gt;
Cc: Kevin Mullican &lt;kevin@mullican.com&gt;
Signed-off-by: Shao Fu &lt;shaofu@realtek.com&gt;
Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: Stable &lt;stable@vger.kernel.org&gt;  [3.18+]
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>brcmfmac: disable MBSS feature for BCM43362</title>
<updated>2015-03-21T06:36:07Z</updated>
<author>
<name>Arend van Spriel</name>
<email>arend@broadcom.com</email>
</author>
<published>2015-03-20T21:18:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f93a25b38cbd840f26c9fd2dd8a6611a57b259b7'/>
<id>urn:sha1:f93a25b38cbd840f26c9fd2dd8a6611a57b259b7</id>
<content type='text'>
The BCM43362 firmware falsely reports it is capable of providing
MBSS. As a result AP mode no longer works for this device. Therefor
disable MBSS in the driver for this chipset.

Cc: stable@vger.kernel.org # 3.19.y
Reported-by: Jorg Krause &lt;jkrause@posteo.de&gt;
Reviewed-by: Hante Meuleman &lt;meuleman@broadcom.com&gt;
Reviewed-by: Pieter-Paul Giesberts &lt;pieterpg@broadcom.com&gt;
Signed-off-by: Arend van Spriel &lt;arend@broadcom.com&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>iwlwifi: mvm: remove WARN_ON for invalid BA notification</title>
<updated>2015-03-19T13:43:11Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2015-03-06T08:17:37Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1f16ea294d2ef63013740f4c8539e430b6c12dff'/>
<id>urn:sha1:1f16ea294d2ef63013740f4c8539e430b6c12dff</id>
<content type='text'>
The firmware frequently manages to trigger this, and there's
no known driver workaround, so stop warning.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>iwlwifi: add new 3165 series PCI IDs</title>
<updated>2015-03-19T12:53:43Z</updated>
<author>
<name>Oren Givon</name>
<email>oren.givon@intel.com</email>
</author>
<published>2015-03-19T10:46:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=132fee062655e90948e189c8c14ce21f115ebbda'/>
<id>urn:sha1:132fee062655e90948e189c8c14ce21f115ebbda</id>
<content type='text'>
Add new 3165 PCI IDs for new 1x1 cards.

Signed-off-by: Oren Givon &lt;oren.givon@intel.com&gt;
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>iwlwifi: mvm: protect rate scaling against non-mvm IBSS stations</title>
<updated>2015-03-19T12:53:35Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2015-03-10T20:24:34Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=dcbc17ad7c7525ed04a45a94cfc5640d5cccf480'/>
<id>urn:sha1:dcbc17ad7c7525ed04a45a94cfc5640d5cccf480</id>
<content type='text'>
When the driver callback returns that it's out of space for new
stations, the mac80211 IBSS code still keeps the station so it
doesn't try to add it over and over again.

Since the rate scaling algorithm is separate in mac80211, it also
invokes the rate scaling algorithm for such stations. It doesn't
know that our rate scaling algorithm is tightly integrated with
the MVM code and relies on those data structures, and it cannot
as the abstraction doesn't allow for it.

This leads to crashes when the rate scaling algorithm tries to
use uninitialized data, notably the mvmsta-&gt;vif pointer.

Protect against this in the rate scaling algorithm. We cannot get
good rates with such peers anyway since the firmware cannot do
anything with them.

This should fix https://bugzilla.kernel.org/show_bug.cgi?id=93461

CC: &lt;stable@vger.kernel.org&gt;
Reported-by: Richard Taylor &lt;rjt-kernel@thegrindstone.me.uk&gt;
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
</feed>
