Re: the select system call's implementation may have some bug inpreempt kernel mode

[Thomas Gleixner]

On Fri, 9 Oct 2009, wu Jianfeng wrote:

> > Right, but that does not cause the task to be scheduled out for ever.
> 
> I don't know why ???
> the process state is TASK_INTERRUPTIBLE, and was scheduled out.
> 
> if no one wake up it or any signals received, it will sleep for ever.
> The process does't entered any file's wait queue at that point, so I
> am sure no one will wake up it.
> 
> Am i right?

No. Did you actually read, what I wrote further down ?
 
> > When the task is scheduled out at that point, it is not
> > deactivated. It is preempted, which means it stays on the run queue
> > despite of the TASK_INTERRUPTIBLE state and is scheduled back in later
> > on.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/