1. 06 4月, 2016 2 次提交
  2. 05 4月, 2016 3 次提交
  3. 05 3月, 2016 1 次提交
  4. 24 2月, 2016 10 次提交
  5. 23 2月, 2016 2 次提交
  6. 30 1月, 2016 2 次提交
    • J
      cfg80211/wext: fix message ordering · cb150b9d
      Johannes Berg 提交于
      Since cfg80211 frequently takes actions from its netdev notifier
      call, wireless extensions messages could still be ordered badly
      since the wext netdev notifier, since wext is built into the
      kernel, runs before the cfg80211 netdev notifier. For example,
      the following can happen:
      
      5: wlan1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default
          link/ether 02:00:00:00:01:00 brd ff:ff:ff:ff:ff:ff
      5: wlan1: <BROADCAST,MULTICAST,UP>
          link/ether
      
      when setting the interface down causes the wext message.
      
      To also fix this, export the wireless_nlevent_flush() function
      and also call it from the cfg80211 notifier.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      cb150b9d
    • J
      wext: fix message delay/ordering · 8bf86273
      Johannes Berg 提交于
      Beniamino reported that he was getting an RTM_NEWLINK message for a
      given interface, after the RTM_DELLINK for it. It turns out that the
      message is a wireless extensions message, which was sent because the
      interface had been connected and disconnection while it was deleted
      caused a wext message.
      
      For its netlink messages, wext uses RTM_NEWLINK, but the message is
      without all the regular rtnetlink attributes, so "ip monitor link"
      prints just rudimentary information:
      
      5: wlan1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default
          link/ether 02:00:00:00:01:00 brd ff:ff:ff:ff:ff:ff
      Deleted 5: wlan1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
          link/ether 02:00:00:00:01:00 brd ff:ff:ff:ff:ff:ff
      5: wlan1: <BROADCAST,MULTICAST,UP>
          link/ether
      (from my hwsim reproduction)
      
      This can cause userspace to get confused since it doesn't expect an
      RTM_NEWLINK message after RTM_DELLINK.
      
      The reason for this is that wext schedules a worker to send out the
      messages, and the scheduling delay can cause the messages to get out
      to userspace in different order.
      
      To fix this, have wext register a netdevice notifier and flush out
      any pending messages when netdevice state changes. This fixes any
      ordering whenever the original message wasn't sent by a notifier
      itself.
      
      Cc: stable@vger.kernel.org
      Reported-by: NBeniamino Galvani <bgalvani@redhat.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      8bf86273
  7. 27 1月, 2016 1 次提交
  8. 14 1月, 2016 4 次提交
    • G
      cfg80211/mac80211: use to_delayed_work · a85a7e28
      Geliang Tang 提交于
      Use to_delayed_work() instead of open-coding it.
      Signed-off-by: NGeliang Tang <geliangtang@163.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      a85a7e28
    • J
      cfg80211: remove CFG80211_REG_DEBUG · c799ba6e
      Johannes Berg 提交于
      Instead of having this Kconfig option, which just *floods* the
      kernel log,
       * remove the per-channel prints that are fairly useless anyway
       * convert the conditional printing to pr_debug()
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      c799ba6e
    • J
      regulatory: fix world regulatory domain data · c3826807
      Johannes Berg 提交于
      The rule definitions here aren't really valid, they would
      be rejected if it came from userspace due to the bandwidth
      specified being bigger than the rule's width.
      
      This is fairly much inconsequential since the other rules
      around them do enable the bandwidth, but express that better
      using the NL80211_RRF_AUTO_BW flag.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      c3826807
    • D
      wireless: change cfg80211 regulatory domain info as debug messages · 94c4fd64
      Dave Young 提交于
      cfg80211 module prints a lot of messages like below. Actually printing
      once is acceptable but sometimes it will print again and again, it looks
      very annoying. It is better to change these detail messages to debugging
      only.
      
      cfg80211: World regulatory domain updated:
      cfg80211:  DFS Master region: unset
      cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
      cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
      cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
      cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
      cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
      cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
      cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
      cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
      cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
      
      The changes in this patch is to replace pr_info with pr_debug in function
      print_rd_rules and print_regdomain_info
      Signed-off-by: NDave Young <dyoung@redhat.com>
      [change some pr_err() statements to at least keep the alpha2]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      94c4fd64
  9. 15 12月, 2015 3 次提交
  10. 04 12月, 2015 11 次提交
  11. 03 11月, 2015 1 次提交