On Mon, 2008-06-23 at 13:17 +0200, Ivo Van Doorn wrote: > Well it was caused by the recent introduction of the interface iterator. > Question now is if we need to restrict the usage, remove the flush_workqueue, > or change the locking in the interface iterator. :S Ouch. Any way you can use the atomic iterator there? Or if not, can you use schedule_work and cancel_work_sync to take care of things? I would like to keep the mac80211 workqueue rtnl-free because otherwise locking is going to get ugly. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
