1. 26 Nov, 2012 4 commits
  2. 23 Nov, 2012 5 commits
  3. 21 Nov, 2012 1 commit
  4. 20 Nov, 2012 1 commit
    • Johannes Berg's avatar
      mac80211: fix channel context suspend/reconfig handling · fe5f2559
      Johannes Berg authored
      
      
      Sujith reported warnings with suspend/resume due to
      channel contexts. When I looked into it, I realised
      that the code was completely broken as it unassigned
      the channel contexts when suspending, which actually
      means they are destroyed.
      
      Eliad Peller then pointed out that we also need to
      remove the channel contexts from the driver. When I
      looked into this, I also noticed that the code isn't
      handling the virtual monitor interface correctly (if
      it exists.)
      
      Fix this by calling just the driver methods (if they
      are implemented) instead of using the channel context
      management code. Also add reconfiguration for the
      virtual monitor interface.
      Reported-by: default avatarSujith Manoharan <sujith@msujith.org>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      fe5f2559
  5. 19 Nov, 2012 6 commits
  6. 13 Nov, 2012 1 commit
  7. 12 Nov, 2012 1 commit
  8. 09 Nov, 2012 5 commits
  9. 07 Nov, 2012 7 commits
  10. 06 Nov, 2012 2 commits
  11. 05 Nov, 2012 5 commits
  12. 30 Oct, 2012 2 commits
    • Johannes Berg's avatar
      mac80211: use a counter for remain-on-channel cookie · 50febf6a
      Johannes Berg authored
      
      
      Instead of using the pointer which can be re-used
      fairly quickly due to allocator patterns and then
      makes debugging difficult, maintain a counter and
      use its value. Since it's a 64-bit value it can't
      really wrap, but catch that case anyway since it
      most likely points to a bug somewhere.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      50febf6a
    • Johannes Berg's avatar
      mac80211: combine status/drop reporting · 8a2fbedc
      Johannes Berg authored
      
      
      The TX status reporting is done for both the
      nl80211 report as well as the socket option.
      The socket option is also reported when an
      skb is dropped to guarantee that the copy in
      the IDR tree is freed and status is reported
      to userspace.
      
      However, when a frame is dropped, no nl80211
      status is reported. This can cause userspace
      to stop making progress while waiting for a
      status notification.
      
      Combine the nl80211 and socket option status
      reporting into a new function and call it in
      both places -- when the status comes in from
      the driver and when the skb is dropped.
      
      While at it, also simplify the code in the
      nl80211 portion a bit.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      8a2fbedc