Re: [PATCH 2/3] make cancel_xxx_work_sync() return a boolean

On Sun, Jul 01, 2007 at 07:37:10PM +0400, Oleg Nesterov wrote: > Change cancel_work_sync() and cancel_delayed_work_sync() to return a boolean > indicating whether the work was actually cancelled. A zero return value means > that the work was not pending/queued. > > Without that kind of change it

Re: [PATCH 2/3] make cancel_xxx_work_sync() return a boolean

On Sun, Jul 01, 2007 at 07:37:10PM +0400, Oleg Nesterov wrote: Change cancel_work_sync() and cancel_delayed_work_sync() to return a boolean indicating whether the work was actually cancelled. A zero return value means that the work was not pending/queued. Without that kind of change it is

[PATCH 2/3] make cancel_xxx_work_sync() return a boolean

Change cancel_work_sync() and cancel_delayed_work_sync() to return a boolean indicating whether the work was actually cancelled. A zero return value means that the work was not pending/queued. Without that kind of change it is not possible to avoid flush_workqueue() sometimes, see the next patch

[PATCH 2/3] make cancel_xxx_work_sync() return a boolean

Change cancel_work_sync() and cancel_delayed_work_sync() to return a boolean indicating whether the work was actually cancelled. A zero return value means that the work was not pending/queued. Without that kind of change it is not possible to avoid flush_workqueue() sometimes, see the next patch