linux.git/net/wireless/core.c, branch v2.6.30

cfg80211: fix locking in nl80211_set_wiphy

2009-03-28T00:13:20+00:00

Luis reports that there's a circular locking dependency;
this is because cfg80211_dev_rename() will acquire the
cfg80211_mutex while the device mutex is held, while
this normally is done the other way around. The solution
is to open-code the device-getting in nl80211_set_wiphy
and require holding the mutex around cfg80211_dev_rename
rather than acquiring it within.

Also fix a bug -- rtnl locking is expected by drivers so
we need to provide it.

Reported-by: Luis R. Rodriguez 
Signed-off-by: Johannes Berg 
Signed-off-by: John W. Linville

cfg80211: add regulatory netlink multicast group

2009-03-16T22:09:40+00:00

This allows us to send to userspace "regulatory" events.
For now we just send an event when we change regulatory domains.
We also notify userspace when devices are using their own custom
world roaming regulatory domains.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: move enum reg_set_by to nl80211.h

2009-03-16T22:09:40+00:00

We do this so we can later inform userspace who set the
regulatory domain and provide details of the request.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: Add AP beacon regulatory hints

2009-02-27T19:52:59+00:00

When devices are world roaming they cannot beacon or do active scan
on 5 GHz or on channels 12, 13 and 14 on the 2 GHz band. Although
we have a good regulatory API some cards may _always_ world roam, this
is also true when a system does not have CRDA present. Devices doing world
roaming can still passive scan, if they find a beacon from an AP on
one of the world roaming frequencies we make the assumption we can do
the same and we also remove the passive scan requirement.

This adds support for providing beacon regulatory hints based on scans.
This works for devices that do either hardware or software scanning.
If a channel has not yet been marked as having had a beacon present
on it we queue the beacon hint processing into the workqueue.

All wireless devices will benefit from beacon regulatory hints from
any wireless device on a system including new devices connected to
the system at a later time.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: make regulatory_request use wiphy_idx instead of wiphy

2009-02-27T19:52:56+00:00

We do this so later on we can move the pending requests onto a
workqueue. By using the wiphy_idx instead of the wiphy we can
later easily check if the wiphy has disappeared or not.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: add assert_cfg80211_lock() to ensure proper protection

2009-02-27T19:52:56+00:00

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: rename cfg80211_drv_mutex to cfg80211_mutex

2009-02-27T19:52:55+00:00

cfg80211_drv_mutex is protecting more than the driver list,
this renames it and documents what its currently supposed to
protect.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: add wiphy_idx_valid to check for wiphy_idx sanity

2009-02-27T19:52:54+00:00

This will later be used by others, for now make use of it in
cfg80211_drv_by_wiphy_idx() to return early if an invalid
wiphy_idx has been provided.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: rename cfg80211_registered_device's idx to wiphy_idx

2009-02-27T19:52:54+00:00

Makes it clearer to read when comparing to ifidx

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville

cfg80211: free_priv for BSS info

2009-02-13T18:45:53+00:00

When cfg80211 users have their own allocated data in the per-BSS
private data, they will need to free this when the BSS struct is
destroyed. Add a free_priv method and fix one place where the BSS
was kfree'd rather than released properly.

Signed-off-by: Johannes Berg 
Signed-off-by: John W. Linville