libata-core.c: unsafe cancel_delayed_work() usage?
- From: Oleg Nesterov <oleg@xxxxxxxxxx>
- Date: Wed, 2 May 2007 02:56:54 +0400
On 04/27, Andrew Morton wrote:
It'd be good if people could take some time to sit down and re-review the
code which we presently have. I plan on sending it all off for 2.6.22 and
there might be some glitches but it seems to have a good track record so
far.
Alan, the usage of cancel_delayed_work() in drivers/ata/libata-core.c looks
suspicious to me, both ->hotplug_task and ->port_task can re-arm themselves,
so cancel_delayed_work + flush_workqueue (or cancel_work_sync) is not enough.
Could you confirm/nack my understanding?
Oleg.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: libata-core.c: unsafe cancel_delayed_work() usage?
- From: Jeff Garzik
- Re: libata-core.c: unsafe cancel_delayed_work() usage?
- Prev by Date: Re: [patch 06/33] m68k: CROSS_COMPILE = m68k-linux-gnu-
- Next by Date: Re: [linux-dvb] DST/BT878 module customization (.. was: Critical points about ...)
- Previous by thread: [PATCH 1/2] ds1wm: simplify platform_data
- Next by thread: Re: libata-core.c: unsafe cancel_delayed_work() usage?
- Index(es):