lkml.org 
[lkml]   [2009]   [Dec]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Warn people about flush_scheduled_work()
On Mon, 14 Dec 2009, Oliver Neukum wrote:

> Am Montag, 14. Dezember 2009 22:33:38 schrieb Alan Stern:
> > Consider using cancel_work_sync() or cancel_delayed_work_sync()
> > instead. In most situations they will accomplish what you
> > need.
>
> In which respect is cancel_work_sync() fundamentally safer?
> If the work is already running and takes a lock you are holding,
> then what?

With cancel_work_sync() you _know_ what locks the work item is going to
take, since it's your work item. With flush_scheduled_work() you have
no idea what locks will be needed by the items on the queue. They
could come from anywhere.

Alan Stern



\
 
 \ /
  Last update: 2009-12-14 23:05    [W:0.079 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site