1. 20 Mar, 2013 1 commit
  2. 11 Mar, 2013 1 commit
  3. 07 Mar, 2013 2 commits
  4. 06 Mar, 2013 1 commit
    • Johannes Berg's avatar
      mac80211: always synchronize_net() during station removal · 27a737ff
      Johannes Berg authored
      If there are keys left during station removal, then a
      synchronize_net() will be done (for each key, I have a
      patch to address this for 3.10), otherwise it won't be
      done at all which causes issues because the station
      could be used for TX while it's being removed from the
      driver -- that might confuse the driver.
      
      Fix this by always doing synchronize_net() if no key
      was present any more.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      27a737ff
  5. 02 Mar, 2013 1 commit
  6. 01 Mar, 2013 3 commits
    • Johannes Berg's avatar
      mac80211: fix VHT MCS calculation · 24af717c
      Johannes Berg authored
      The VHT MCSes we advertise to the AP were supposed to
      be restricted to the AP, but due to a bug in the logic
      mac80211 will advertise rates to the AP that aren't
      even supported by the local device. To fix this skip
      any adjustment if the NSS isn't supported at all.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      24af717c
    • Marco Porsch's avatar
      mac80211: fix oops on mesh PS broadcast forwarding · 7cbf9d01
      Marco Porsch authored
      Introduced with de74a1d9
      "mac80211: fix WPA with VLAN on AP side with ps-sta".
      Apparently overwrites the sdata pointer with non-valid data in
      the case of mesh.
      Fix this by checking for IFTYPE_AP_VLAN.
      Signed-off-by: default avatarMarco Porsch <marco@cozybit.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      7cbf9d01
    • Johannes Berg's avatar
      nl80211: increase wiphy dump size dynamically · 645e77de
      Johannes Berg authored
      Given a device with many channels capabilities the wiphy
      information can still overflow even though its size in
      3.9 was reduced to 3.8 levels. For new userspace and
      kernel 3.10 we're going to implement a new "split dump"
      protocol that can use multiple messages per wiphy.
      
      For now though, add a workaround to be able to send more
      information to userspace. Since generic netlink doesn't
      have a way to set the minimum dump size globally, and we
      wouldn't really want to set it globally anyway, increase
      the size only when needed, as described in the comments.
      As userspace might not be prepared for large buffers, we
      can only use 4k.
      
      Also increase the size for the get_wiphy command.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      645e77de
  7. 28 Feb, 2013 1 commit
  8. 27 Feb, 2013 1 commit
  9. 26 Feb, 2013 5 commits
  10. 25 Feb, 2013 4 commits
  11. 22 Feb, 2013 3 commits
  12. 18 Feb, 2013 17 commits