On Fri, Dec 03, 2010 at 12:24:44AM +0530, John W. Linville wrote: > On Tue, Nov 30, 2010 at 04:36:37PM +0530, Rajkumar Manoharan wrote: > > While releasing beacon slot, it can be accessed by beacon tasklet. > > To avoid concurrency, beacon alert is disabled before > > freeing beacon resource and it will be enabled again in the > > persence of other beaconing mode interfaces. > > > > Signed-off-by: Rajkumar Manoharan <rmanoharan@xxxxxxxxxxx> > > Is this intended for 2.6.37? It looks like it could apply there. yes. I missed to mention. Thanks for pointing out. > Could you be more specific about the effect of the bug you are fixing? The beacon tasklet is accesssing the bslot info for beacon generation. Meanwhile the same slot can be freed on interface deletion. Actually the remove_interface disables the beacon alert after freeing the slot. This may lead to null pointer access. This patch disables SWBA and kills the beacon tasklet to prevent access to the slot to be freed. After releasing the slot, swba will be enabled again upon the availablity of beaconing interfaces. -- Rajkumar -- 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
