Re: One more boobytrap needed for 2.2.15pre ?

From: Manfred Spraul (manfreds@colorfullife.com)
Date: Tue Feb 15 2000 - 16:37:19 EST


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/



This archive was generated by hypermail 2b29 : Tue Feb 15 2000 - 21:00:30 EST