On 02/26/2013 08:05 AM, Stanislaw Gruszka wrote:
On Wed, Feb 20, 2013 at 09:41:09AM -0800, greearb@xxxxxxxxxxxxxxx wrote:
From: Ben Greear <greearb@xxxxxxxxxxxxxxx>
The monitor_work and beacon_connection_loss_work items were
not being canceled on disassociation (and not on deletion
either). This leads to work-items trying to run after memory
has been deleted.
[skip]
+ /* Make sure some work items will not run after this.
+ * Have to do this outside the ifmgd->mtx lock.
+ */
+ cancel_work_sync(&ifmgd->monitor_work);
+ cancel_work_sync(&ifmgd->beacon_connection_loss_work);
Other works should be canceled as well. Ben, could you repost
this patch with proper comment?
At least in 3.7 kernel, this seems to be all that is needed.
I don't have much time to work on this now...
Thanks,
Ben
Stanislaw
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
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
