1. 26 8月, 2010 1 次提交
    • J
      nl80211: fix missing nesting · 74b70a4e
      Johannes Berg 提交于
      commit 95a6ccbb46c70cff376684c752831c014c87029d
      Author: Johannes Berg <johannes.berg@intel.com>
      Date:   Thu Aug 12 15:38:38 2010 +0200
      
          cfg80211/mac80211: extensible frame processing
      
      introduced a netlink bug that caused parsing errors
      in userspace because it forgot to close a nesting,
      which would advertise a nesting length of zero to
      userspace, which then completely threw off parsing
      and led to
      
      	Illegal nla->nla_type == 0
      
      being printed by libnl.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      74b70a4e
  2. 25 8月, 2010 2 次提交
  3. 17 8月, 2010 4 次提交
  4. 10 8月, 2010 1 次提交
  5. 29 7月, 2010 2 次提交
  6. 28 7月, 2010 1 次提交
    • J
      wireless: Convert wiphy_debug macro to function · 073730d7
      Joe Perches 提交于
      Save a few bytes of text
      
      (allyesconfig)
      $ size drivers/net/wireless/built-in.o*
         text	   data	    bss	    dec	    hex	filename
      3924568	 100548	 871056	4896172	 4ab5ac	drivers/net/wireless/built-in.o.new
      3926520	 100548	 871464	4898532	 4abee4	drivers/net/wireless/built-in.o.old
      
      $ size net/wireless/core.o*
         text	   data	    bss	    dec	    hex	filename
        12843	    216	   3768	  16827	   41bb	net/wireless/core.o.new
        12328	    216	   3656	  16200	   3f48	net/wireless/core.o
      Signed-off-by: NJoe Perches <joe@perches.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      073730d7
  7. 27 7月, 2010 3 次提交
  8. 22 7月, 2010 1 次提交
  9. 21 7月, 2010 6 次提交
  10. 15 7月, 2010 1 次提交
  11. 13 7月, 2010 1 次提交
  12. 08 7月, 2010 1 次提交
    • J
      NET: nl80211, fix lock imbalance and netdev referencing · 60ea385f
      Jiri Slaby 提交于
      Stanse found that nl80211_set_wiphy imporperly handles a lock and netdev
      reference and contains unreachable code. It is because there return statement
      isntead of assignment to result variable. Fix that.
      Signed-off-by: NJiri Slaby <jirislaby@gmail.com>
      Cc: Johannes Berg <johannes@sipsolutions.net>
      Cc: "John W. Linville" <linville@tuxdriver.com>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Jouni Malinen <j@w1.fi>
      Cc: Samuel Ortiz <sameo@linux.intel.com>
      Cc: linux-wireless@vger.kernel.org
      Cc: netdev@vger.kernel.org
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      60ea385f
  13. 25 6月, 2010 3 次提交
  14. 19 6月, 2010 2 次提交
  15. 16 6月, 2010 1 次提交
  16. 15 6月, 2010 2 次提交
  17. 03 6月, 2010 2 次提交
  18. 22 5月, 2010 3 次提交
  19. 08 5月, 2010 1 次提交
    • J
      cfg80211/mac80211: better channel handling · f444de05
      Johannes Berg 提交于
      Currently (all tested with hwsim) you can do stupid
      things like setting up an AP on a certain channel,
      then adding another virtual interface and making
      that associate on another channel -- this will make
      the beaconing to move channel but obviously without
      the necessary IEs data update.
      
      In order to improve this situation, first make the
      configuration APIs (cfg80211 and nl80211) aware of
      multi-channel operation -- we'll eventually need
      that in the future anyway. There's one userland API
      change and one API addition. The API change is that
      now SET_WIPHY must be called with virtual interface
      index rather than only wiphy index in order to take
      effect for that interface -- luckily all current
      users (hostapd) do that. For monitor interfaces, the
      old setting is preserved, but monitors are always
      slaved to other devices anyway so no guarantees.
      
      The second userland API change is the introduction
      of a per virtual interface SET_CHANNEL command, that
      hostapd should use going forward to make it easier
      to understand what's going on (it can automatically
      detect a kernel with this command).
      
      Other than mac80211, no existing cfg80211 drivers
      are affected by this change because they only allow
      a single virtual interface.
      
      mac80211, however, now needs to be aware that the
      channel settings are per interface now, and needs
      to disallow (for now) real multi-channel operation,
      which is another important part of this patch.
      
      One of the immediate benefits is that you can now
      start hostapd to operate on a hardware that already
      has a connection on another virtual interface, as
      long as you specify the same channel.
      
      Note that two things are left unhandled (this is an
      improvement -- not a complete fix):
      
       * different HT/no-HT modes
      
         currently you could start an HT AP and then
         connect to a non-HT network on the same channel
         which would configure the hardware for no HT;
         that can be fixed fairly easily
      
       * CSA
      
         An AP we're connected to on a virtual interface
         might indicate switching channels, and in that
         case we would follow it, regardless of how many
         other interfaces are operating; this requires
         more effort to fix but is pretty rare after all
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      f444de05
  20. 28 4月, 2010 2 次提交