1. 30 Nov, 2012 1 commit
    • Johannes Berg's avatar
      cfg80211: fix BSS struct IE access races · 9caf0364
      Johannes Berg authored
      When a BSS struct is updated, the IEs are currently
      overwritten or freed. This can lead to races if some
      other CPU is accessing the BSS struct and using the
      IEs concurrently.
      
      Fix this by always allocating the IEs in a new struct
      that holds the data and length and protecting access
      to this new struct with RCU.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      9caf0364
  2. 27 Nov, 2012 1 commit
  3. 26 Nov, 2012 2 commits
    • Johannes Berg's avatar
      mac80211: convert to channel definition struct · 4bf88530
      Johannes Berg authored
      Convert mac80211 (and where necessary, some drivers a
      little bit) to the new channel definition struct.
      
      This will allow extending mac80211 for VHT, which is
      currently restricted to channel contexts since there
      are no drivers using that which makes it easier. As
      I also don't care about VHT for drivers not using the
      channel context API, I won't convert the previous API
      to VHT support.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      4bf88530
    • Johannes Berg's avatar
      mac80211: fix managed mode channel flags handling · 028e8da0
      Johannes Berg authored
      If ieee80211_prep_channel() decides that HT should be
      disabled (because the HT IEs from the AP were invalid)
      it will set the IEEE80211_STA_DISABLE_HT to not send
      HT capabilities to the AP when associating. If this
      happens during authentication, the flag will be lost
      and we send HT frames, even if the channel config was
      set up for non-HT. This can lead to issues.
      
      Fix this by always resetting the ifmgd flags to zero
      when the channel context is released so that the flag
      resetting in ieee80211_mgd_assoc() isn't necessary.
      
      To make the code a bit easier move the call to release
      the channel in ieee80211_set_disassoc() to the end of
      the function together with the flag resetting (which
      needs to be at the end to avoid timers setting flags.)
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      028e8da0
  4. 23 Nov, 2012 3 commits
    • Johannes Berg's avatar
      mac80211: disable HT advertising unless AP supports it · 03ae834f
      Johannes Berg authored
      If the AP doesn't support HT, or more importantly if
      it does but we have to disable it because its IEs are
      broken, don't advertise HT support in our association
      request. Otherwise, we configure our channel to be a
      20 MHz non-HT channel but the AP might still think we
      support HT, or even 40 MHz.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      03ae834f
    • Johannes Berg's avatar
      mac80211: rename IEEE80211_STA_DISABLE_11N to HT · a8243b72
      Johannes Berg authored
      Since the 11n spec amendment was rolled into the
      2012 version, "11n" no longer makes sense. Use
      "HT" instead.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      a8243b72
    • Johannes Berg's avatar
      mac80211: fix RX chains configuration · 76c5fa0f
      Johannes Berg authored
      If the driver doesn't support 40 MHz channels, then
      mac80211 erroneously sets number of RX chains to one
      although the number of chains is independent of the
      support for 40 MHz channels.
      
      Fix this by checking the 40 MHz support only for the
      code that sets the 40 MHz channel not the complete
      HT code block.
      
      This also means the HT20 channel type will always be
      set in the changed code block so there's no need to
      set it in case we override the AP due to invalid IEs
      in the probe response/beacon.
      
      The indentation is a bit quirky, but I'm rewriting
      this code for VHT support so this will change again
      very soon.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      76c5fa0f
  5. 06 Nov, 2012 1 commit
  6. 05 Nov, 2012 1 commit
    • Johannes Berg's avatar
      mac80211: send deauth only with channel context · 86552017
      Johannes Berg authored
      When userspace asks to deauthenticate and we're just
      authenticated (or still authenticating) send a deauth
      frame instead of deleting the auth request.
      
      On the other hand, if we've just disassociated and
      therefore deleted all our state already, drop the
      deauth request because we no longer have a channel
      context to send it on.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      86552017
  7. 30 Oct, 2012 1 commit
    • Johannes Berg's avatar
      mac80211: handle TX power per virtual interface · 1ea6f9c0
      Johannes Berg authored
      Even before channel contexts/multi-channel, having a
      single global TX power limit was already problematic,
      in particular if two managed interfaces connected to
      two APs with different power constraints. The channel
      context introduction completely broke this though and
      in fact I had disabled TX power configuration there
      for drivers using channel contexts.
      
      Change everything to track TX power per interface so
      that different user settings and different channel
      maxima are treated correctly. Also continue tracking
      the global TX power though for compatibility with
      applications that attempt to configure the wiphy's
      TX power globally.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      1ea6f9c0
  8. 25 Oct, 2012 1 commit
  9. 18 Oct, 2012 1 commit
  10. 17 Oct, 2012 8 commits
  11. 15 Oct, 2012 1 commit
  12. 21 Sep, 2012 1 commit
  13. 14 Sep, 2012 2 commits
  14. 07 Sep, 2012 1 commit
  15. 06 Sep, 2012 2 commits
  16. 04 Sep, 2012 1 commit
  17. 20 Aug, 2012 6 commits
  18. 01 Aug, 2012 2 commits
  19. 31 Jul, 2012 4 commits