forked from mirrors/linux
		
	wifi: cfg80211: use system_unbound_wq for wiphy work
Since wiphy work items can run pretty much arbitrary
code in the stack/driver, it can take longer to run
all of this, so we shouldn't be using system_wq via
schedule_work(). Also, we lock the wiphy (which is
the reason this exists), so use system_unbound_wq.
Reported-and-tested-by: Kalle Valo <kvalo@kernel.org>
Fixes: a3ee4dc84c ("wifi: cfg80211: add a work abstraction with special semantics")
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
			
			
This commit is contained in:
		
							parent
							
								
									f291209eca
								
							
						
					
					
						commit
						91d20ab9d9
					
				
					 1 changed files with 1 additions and 1 deletions
				
			
		|  | @ -1622,7 +1622,7 @@ void wiphy_work_queue(struct wiphy *wiphy, struct wiphy_work *work) | ||||||
| 		list_add_tail(&work->entry, &rdev->wiphy_work_list); | 		list_add_tail(&work->entry, &rdev->wiphy_work_list); | ||||||
| 	spin_unlock_irqrestore(&rdev->wiphy_work_lock, flags); | 	spin_unlock_irqrestore(&rdev->wiphy_work_lock, flags); | ||||||
| 
 | 
 | ||||||
| 	schedule_work(&rdev->wiphy_work); | 	queue_work(system_unbound_wq, &rdev->wiphy_work); | ||||||
| } | } | ||||||
| EXPORT_SYMBOL_GPL(wiphy_work_queue); | EXPORT_SYMBOL_GPL(wiphy_work_queue); | ||||||
| 
 | 
 | ||||||
|  |  | ||||||
		Loading…
	
		Reference in a new issue
	
	 Johannes Berg
						Johannes Berg