Re: [PATCH] fix loop with disabled tasklets

[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?