linux-stable.git/net/wireless, branch linux-2.6.29.y

cfg80211: fix race between core hint and driver's custom apply

2009-06-15T16:40:02+00:00

commit 5078b2e32ad4b1f753b1c837c15892202f753c97 upstream.

Its possible for cfg80211 to have scheduled the work and for
the global workqueue to not have kicked in prior to a cfg80211
driver's regulatory hint or wiphy_apply_custom_regulatory().

Although this is very unlikely its possible and should fix
this race. When this race would happen you are expected to have
hit a null pointer dereference panic.

Signed-off-by: Luis R. Rodriguez 
Tested-by: Alan Jenkins 
Signed-off-by: John W. Linville 
Signed-off-by: Greg Kroah-Hartman

cfg80211: fix incorrect assumption on last_request for 11d

2009-04-02T20:55:19+00:00

upstream commit: cc0b6fe88e99096868bdbacbf486c97299533b5a

The incorrect assumption is the last regulatory request
(last_request) is always a country IE when processing
country IEs. Although this is true 99% of the time the
first time this happens this could not be true.

This fixes an oops in the branch check for the last_request
when accessing drv_last_ie. The access was done under the
assumption the struct won't be null.

Note to stable: to port to 29 replace as follows, only 29 has
country IE code:

s|NL80211_REGDOM_SET_BY_COUNTRY_IE|REGDOM_SET_BY_COUNTRY_IE

Cc: stable@kernel.org
Reported-by: Quentin Armitage 
Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville 
[chrisw: backport to 2.6.29]
Signed-off-by: Chris Wright

cfg80211: force last_request to be set for OLD_REG if regdom is EU

2009-04-02T20:55:17+00:00

upstream commit: 2e097dc65673ed421bbc2e49f52c125aa43a8ee6

Although EU is a bogus alpha2 we need to process the send request
as our code depends on last_request being set.

Cc: stable@kernel.org
Reported-by: Quentin Armitage 
Signed-off-by: Luis R. Rodriguez 
Signed-off-by: John W. Linville 
[chrisw: backport to 2.6.29]
Signed-off-by: Chris Wright 
Port-acked-by: Luis R. Rodriguez

nl80211: Check that function pointer != NULL before using it

2009-03-20T20:01:57+00:00

NL80211_CMD_GET_MESH_PARAMS and NL80211_CMD_SET_MESH_PARAMS handlers
did not verify whether a function pointer is NULL (not supported by
the driver) before trying to call the function. The former nl80211
command is available for unprivileged users, too, so this can
potentially allow normal users to kill networking (or worse..) if
mac80211 is built without CONFIG_MAC80211_MESH=y.

Signed-off-by: Jouni Malinen 
Signed-off-by: John W. Linville

lib80211: silence excessive crypto debugging messages

2009-03-16T22:01:58+00:00

When they were part of the now defunct ieee80211 component, these
messages were only visible when special debugging settings were enabled.
Let's mirror that with a new lib80211 debugging Kconfig option.

Signed-off-by: John W. Linville

cfg80211: test before subtraction on unsigned

2009-03-06T20:54:32+00:00

freq_diff is unsigned, so test before subtraction

Signed-off-by: Roel Kluin 
Signed-off-by: John W. Linville

cfg80211: print correct intersected regulatory domain

2009-01-29T20:46:43+00:00

When CONFIG_CFG80211_REG_DEBUG is enabled and an intersection
occurs we are printing the regulatory domain passed by CRDA
and indicating its the intersected regulatory domain. Lets fix
this and print the intersection as originally intended.

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

cfg80211: Fix sanity check on 5 GHz when processing country IE

2009-01-29T20:46:43+00:00

This fixes two issues with the sanity check loop when processing
the country IE:

1. Do not use frequency for the current subband channel check,
   this was a big fat typo.
2. Apply the 5 GHz 4-channel steps when considering max channel
   on each subband as was done with a recent patch.

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

cfg80211: Fix parsed country IE info for 5 GHz

2009-01-16T22:08:24+00:00

The country IE number of channels on 5 GHz specifies the number
of 5 GHz channels, not the number of sequential channel numbers.
For example, if in a country IEs if the first channel given is 36
and the number of channels passed is 4 then the individual channel
numbers defined for the 5 GHz PHY by these parameters

are: 36, 40, 44, 48
not: 36, 37, 38, 39

See: http://tinyurl.com/11d-clarification

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

cfg80211: Fix regression with 11d on bands

2009-01-16T22:08:24+00:00

This fixes a regression on disallowing bands introduced with the new
802.11d support. The issue is that IEEE-802.11 allows APs to send
a subset of what a country regulatory domain defines. This was clarified
in this document:

http://tinyurl.com/11d-clarification

As such it is possible, and this is what is done in practice, that a
single band 2.4 GHz AP will only send 2.4 GHz band regulatory information
through the 802.11 country information element and then the current
intersection with what CRDA provided yields a regulatory domain with
no 5 GHz information -- even though that country may actually allow
5 GHz operation. We correct this by only applying the intersection rules
on a channel if the the intersection yields a regulatory rule on the
same band the channel is on.

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