On Friday 03 August 2007 00:02:07 Johannes Berg wrote: > Adding to my previous mail, this fix is not enough. As you can see > below, it is never safe to call flush_scheduled_work() under rtnl > because some other things running *from* the global events workqueue > acquire the rtnl and hence it we could deadlock against them. > > I think the fix would be to use cancel_delayed_work_sync() here instead > of a combination of cancel_delayed_work() and flush_workqueue(). Ah, Ok. I didn't see that rtnl is locked there, too. cancel_delayed_work_sync could probably work. Care to test that? -- Greetings Michael. - 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
