Messages in this thread | | | From | "Manfred Spraul" <> | Subject | Re: One more boobytrap needed for 2.2.15pre ? | Date | Tue, 15 Feb 2000 22:37:19 +0100 |
| |
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
> > Ok, but now the question is: which interrupt changes current->state? Perhaps > > a special boobytrap in the interrupt handlers could detect that? > > Numerous interrupt handlers change task->state. Every interrupt handler that > does a wake_up_interruptible() for example. It could easily be 'current'
Yes, my booby-trap was wrong: * wake_up_interruptible() is ok: it add the the task back into the runqueue * changing current->state _without_ adding back into the runqueue causes corruptions.
-- Manfred
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |