On Wed, Jul 02, 2003 at 09:52:15AM +0200, Martin Maletinsky wrote: > However, just out of interest, could you explain me the problems that > could result from the task being on arbitrary wait_queues? I fear it's not possible to correctly set the task state upon interrupt exit. The problem is, that you can't say when other wait_queue was awoken in addition to yours (because you don't know about it's existence). So you will have to leave the task in running state, which wouldn't upset wait_event/wait_event_interruptible, but that shouldn't be relied upon. ------------------------------------------------------------------------------- Jan 'Bulb' Hudec <bulb@ucw.cz> -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
