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 not possible to avoid flush_workqueue()
> sometimes, see the next patch as an example.
> 
> Also, this patch unifies both functions and kills the (unlikely) busy-wait loop.
> 
> Signed-off-by: Oleg Nesterov <[email protected]>

Acked-by: Jarek Poplawski <[email protected]>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH 2/3] make cancel_xxx_work_sync() return a boolean
  - From: Oleg Nesterov <[email protected]>

Prev by Date: how do versioning filesystems take snapshot of opened files?
Next by Date: Re: [PATCH 3/4] usb: allocated usb releated dma buffer with kmalloc_node
Previous by thread: [PATCH 2/3] make cancel_xxx_work_sync() return a boolean
Next by thread: [PATCH 3/3] tty_io.c: don't use flush_scheduled_work()
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]