linux-stable.git/net/wireless/core.c, branch v3.6

cfg80211: process pending events when unregistering net device

2012-08-06T18:29:58+00:00

libertas currently calls cfg80211_disconnected() when it is being
brought down. This causes an event to be allocated, but since the
wdev is already removed from the rdev by the time that the event
processing work executes, the event is never processed or freed.
http://article.gmane.org/gmane.linux.kernel.wireless.general/95666

Fix this leak, and other possible situations, by processing the event
queue when a device is being unregistered. Thanks to Johannes Berg for
the suggestion.

Signed-off-by: Daniel Drake 
Cc: stable@vger.kernel.org
Reviewed-by: Johannes Berg 
Signed-off-by: John W. Linville

cfg80211: make regulatory_update() static

2012-07-17T10:16:40+00:00

Now that we have wiphy_regulatory_register() we can
tuck away the core's regulatory_update() call there
and make it static.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: Johannes Berg

cfg80211: rename reg_device_remove() to wiphy_regulatory_deregister()

2012-07-17T10:16:39+00:00

This makes it clearer what we're doing. This now makes a bit
more sense given that regardless of the wiphy if the cell
base station hint feature is supported we will be modifying the
way the regulatory core behaves.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: Johannes Berg

cfg80211: add cellular base station regulatory hint support

2012-07-17T10:16:39+00:00

Cellular base stations can provide hints to cfg80211 about
where they think we are. This can be done for example on
a cell phone. To enable these hints we simply allow them
through as user regulatory hints but we allow userspace
to clasify the hint as either coming directly from the
user or coming from a cellular base station. This option
is only available when you enable
CONFIG_CFG80211_CERTIFICATION_ONUS.

The base station hints themselves will not be processed
by the core unless at least one device on the system
supports this feature.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: Johannes Berg

cfg80211: reduce monitor interface tracking

2012-07-13T14:16:11+00:00

Revert commit b78e8ceac23655e1e06b30aa95ab11742d1ac7c0
("cfg80211: track monitor channel") and remove the
set_monitor_enabled() callback.

Due to the tracking happening in NETDEV_PRE_UP, it had
introduced bugs because the monitor interface callback
would be called before the device was started. It looks
like there's no way to fix this, and using NETDEV_PRE_UP
is broken anyway (since there's no NETDEV_UP_FAIL), so
remove all that code, track interfaces in NETDEV_UP and
also stop tracking the monitor channel in cfg80211.

This mostly reverts to before the tracking, except that
we keep the interface count tracking so that setting the
monitor channel can be rejected properly.

Signed-off-by: Johannes Berg

nl80211: move scan API to wdev

2012-07-12T10:10:41+00:00

The new P2P Device will have to be able to scan for
P2P search, so move scanning to use struct wireless_dev
instead of struct net_device.

Signed-off-by: Johannes Berg

nl80211: don't assume wdev->netdev exists

2012-07-09T12:51:46+00:00

There are a few places that iterate the wdev
list and assume wdev->netdev exists, check
there. The rfkill one has to be extended for
each non-netdev type later.

Signed-off-by: Johannes Berg

nl80211: prepare for non-netdev wireless devs

2012-07-09T12:51:46+00:00

In order to support a P2P device abstraction and
Bluetooth high-speed AMPs, we need to have a way
to identify virtual interfaces that don't have a
netdev associated.

Do this by adding a NL80211_ATTR_WDEV attribute
to identify a wdev which may or may not also be
a netdev.

To simplify things, use a 64-bit value with the
high 32 bits being the wiphy index for this new
wdev identifier in the nl80211 API.

Signed-off-by: Johannes Berg

cfg80211: fix oops due to unassigned set_monitor_enabled callback

2012-07-08T11:10:07+00:00

Quick fix for method being invoked without checking its existence.

Signed-off-by: Vladimir Kondratiev 
Signed-off-by: Johannes Berg

cfg80211: fix locking regression in monitor channel tracking

2012-07-04T11:30:23+00:00

Michal's monitor channel tracking introduce a locking problem
as it locked the rdev lock inside the netdev notifier which
isn't allowed as we might already hold it if we get there by
removing an interface that is up.

Fix this by relying only on the RTNL to protect the interface
counters, the RTNL is always held in these code paths anyway.

Signed-off-by: Johannes Berg