Messages in this thread |  | | Subject | Re: [PATCH] fix loop with disabled tasklets | Date | Sat, 10 Nov 2001 16:02:44 +0000 (GMT) | From | Alan Cox <> |
| |
> > queue if it remains disabled forever. tasklet_kill will deadlock on a > > tasklet that is disabled. > I think this is the responsability of the device driver writer (or who ever > uses it). AFAIK there is no defined behavior for this case. I vote for > removing the tasklet without it ever being run.
I don't think the semantics actually matter too much. That would be mostly down to timing. Surely its sufficient to say something like "when tasklet_kill returns the tasklet will not be scheduled or execute further"
Do we care if it ran ? And do we want to imply any locking properties we might have to maintain? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |