On Wed, May 13, 2009 at 05:04:42PM -0400, Luis R. Rodriguez wrote: > 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. > > Cc: stable@xxxxxxxxxx > Signed-off-by: Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> (Same questions as for 3/4...) What is the effect of this race? What justifies this for 2.6.30 and/or stable? It is getting late in the cycle for 2.6.30... John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
