[lkml]   [2000]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Drivers that potentially leave state as TASK_{UN}INTERRUPTIBLE
On Wed, 6 Sep 2000, George Anzinger wrote:

> John Levon wrote:
> >
> > Am I right ? against test8pre1
> >
> > Also, is it a bug to not set TASK_{UN}INTERRUPTIBLE before doing a
> > schedule_timeout() ? What will happen ?
> >
> Well, first the "timeout" call will return immediately. Next, when the
> time out actually happens, if the task is not TASK_RUNNING (i.e. it is
> waiting for some other thing) it will wake_up. So the sleep is lost and
> it is possible to have a false wake up (could even wake up a zombie).
> If the actual timeout happens while the task is TASK_RUNNING it is
> ignored.
> George

So it seems to be a bug at least in terms of timing. Unfortunately I only
got about 4 replies to the patches that touched 20+ drivers. I suppose I
should just hassle maintainers until they fix it or tell me where I've
gone wrong ...


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.051 / U:0.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site